AI agents use patch_matter_archive to create or update resources in Smokeball — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smokeball environment.
This tool creates or modifies data reversibly by updating archive-related metadata fields (like destruction_date) on an existing matter. It does not irreversibly delete data (which would be Destructive) nor does it execute arbitrary code or trigger external operations. The 'archive' terminology refers to metadata state rather than destruction.
From the tool's definition Tool name includes 'patch' (HTTP PATCH method for partial updates) and description states 'Update archive metadata fields on a matter'. The operation modifies metadata via a PATCH request without deleting the matter itself.
Attacks that exploit this kind of access
Update archive metadata fields on a matter (PATCH). destruction_date: YYYY-MM-DD. It is categorised as a Write tool in the Smokeball MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smokeball MCP server in PolicyLayer and add a rule for patch_matter_archive: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Smokeball. Nothing to install.
patch_matter_archive is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the patch_matter_archive rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for patch_matter_archive. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
patch_matter_archive is provided by the Smokeball MCP server (rosenadvertising/smokeball-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →