AI agents use unregister_template to create or update resources in Report — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Report environment.
Unregistering a template from the server cache is a write-class operation because it modifies server state by removing a cache entry. It is not destructive because cache entries are temporary and can be re-registered; the underlying template data persists.
From the tool's definition Tool description states 'Free the server-side cache entry for `template_id`'. The action removes/clears a cached entry, which is a reversible modification of server state (cache can be repopulated).
Attacks that exploit this kind of access
Free the server-side cache entry for template_id. Optional —. It is categorised as a Write tool in the Report MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Report MCP server in PolicyLayer and add a rule for unregister_template: 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 Report. Nothing to install.
unregister_template 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 unregister_template 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 unregister_template. 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.
unregister_template is provided by the Report MCP server (jaykim429/report-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 →