Classification data
A classification request sends event text and the context supplied by your integration. This can include a hook, tool name, conversation ID, request identity, and governance resource context. Tool responses and generated output can contain sensitive application data. Send the context needed to evaluate the protected boundary. Review event construction before production use and remove credentials that the check does not need. Inspect the API schema for supported fields.Credentials
Keep service keys in the protected service’s environment or secret manager. Direct macOS installs save a typed key in the user’s login Keychain. Managed profiles supply the connection values and are readable by MDM administrators. Restrict access to completed profiles. Rotate managed URL and key values together. Local app removal leaves server-side credential revocation to your deployment administrator.Evidence and access
Dashboard findings and captured conversation evidence can contain event content. Restrict evidence access to authorized reviewers and check capture availability when investigating a decision. Firewall MCP provides tenant-scoped evidence tools with separate permissions for restricted detail.Deployment planning
Confirm the following with Silmaril during setup. Record the agreed values in your deployment plan.
Use the privacy policy and your service agreement for applicable terms. See self-hosted deployments for responsibility planning.