mutate_object_schema
Create, update, or delete a Sanka custom object schema through routed arguments. Integration schema mutation is a V2 backend gap and will be rejected by the API.
This record as markdown: /tools/sankahq-sanka-mcp/mutate-object-schema.md
What mutate_object_schema does on Sanka MCP Server
AI agents call mutate_object_schema to permanently remove resources in Sanka MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why mutate_object_schema is rated Critical
While the tool spans Write (create/update) and Destructive (delete) categories, the inclusion of delete operations on schema objects makes this Destructive. Deleting a custom object schema is irreversible and has broad blast radius — it can cascade to dependent records, workflows, and integrations.
From the tool's definition Tool description explicitly states it can 'Create, update, or delete a Sanka custom object schema' — the delete operation is irreversible and affects data structure definitions that likely impact multiple records and workflows.
Attacks that exploit this kind of access
The rule that runs mutate_object_schema safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mutate_object_schema, this is the rule to start with:
mutate_object_schema is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every mutate_object_schema call is checked against it from then on.
Questions about mutate_object_schema
Create, update, or delete a Sanka custom object schema through routed arguments. Integration schema mutation is a V2 backend gap and will be rejected by the API. It is categorised as a Destructive tool in the Sanka MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for mutate_object_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 Sanka MCP Server. Nothing to install.
mutate_object_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 mutate_object_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 mutate_object_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.
mutate_object_schema is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
Across the catalogue