Remove JSON schema from a collection
AI agents call remove_schema to permanently remove resources in Codehooks Io MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes schema validation rules from a collection, which is a destructive operation. While the data itself may persist, removing the schema eliminates critical metadata that governs data structure and validation. This is irreversible in the sense that the schema definition is lost, and recovering it would require external backups or knowledge of the original schema.
From the tool's definition Tool name 'remove_schema' combined with description 'Remove JSON schema from a collection' indicates irreversible deletion of schema metadata.
Documented attack patterns abuse exactly the kind of access remove_schema gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codehooks Io MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_schema:
{
"version": "1",
"default": "deny",
"hide": [
"remove_schema"
]
}remove_schema disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove JSON schema from a collection. It is categorised as a Destructive tool in the Codehooks Io MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Codehooks Io MCP Server MCP server in PolicyLayer and add a rule for remove_schema: 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 Codehooks Io MCP Server. Nothing to install.
remove_schema 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 remove_schema 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 remove_schema. 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.
remove_schema is provided by the Codehooks Io MCP Server MCP server (restdb/codehooks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Codehooks Io MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Codehooks Io MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.