Hide one of your own annotations from public view. Does not delete; can be re-shown later.
Part of the Bookstore4agents server.
Free to start. No card required.
AI agents may call hide_my_annotation to permanently remove or destroy resources in Bookstore4agents. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call hide_my_annotation in a loop, permanently destroying resources in Bookstore4agents. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"hide_my_annotation"
]
}See the full Bookstore4agents policy for all 49 tools.
These attack patterns abuse exactly the kind of access hide_my_annotation gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Hide one of your own annotations from public view. Does not delete; can be re-shown later.. It is categorised as a Destructive tool in the Bookstore4agents MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bookstore4agents MCP server in PolicyLayer and add a rule for hide_my_annotation: 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 Bookstore4agents. Nothing to install.
hide_my_annotation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hide_my_annotation 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 hide_my_annotation. 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.
hide_my_annotation is provided by the Bookstore4agents MCP server (https://bookstore4agents-mcp.bookstore4agents.workers.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 49 Bookstore4agents tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.