Execute multiple operations in a single atomic transaction. All succeed or all fail together.
AI agents invoke sanity_bulk to trigger actions in Sanity MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
sanity_bulk executes arbitrary multiple operations whose effects are determined by caller-supplied arguments. While each individual operation might be categorized as Write, Create, or Delete, the bulk execution capability to perform multiple operations atomically with side effects that extend beyond simple data modification (it controls transaction semantics) elevates this to Execute.
From the tool's definition "Execute multiple operations in a single atomic transaction. All succeed or all fail together." The tool executes multiple operations programmatically; the outcomes depend entirely on which operations are specified as arguments, making this Execute rather…
Attacks that exploit this kind of access
Execute multiple operations in a single atomic transaction. All succeed or all fail together. It is categorised as a Execute tool in the Sanity MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sanity MCP Server MCP server in PolicyLayer and add a rule for sanity_bulk: 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 Sanity MCP Server. Nothing to install.
sanity_bulk is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sanity_bulk 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 sanity_bulk. 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.
sanity_bulk is provided by the Sanity MCP Server MCP server (purple-horizons/sanity-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 →