AI agents use sendook_create_inbox to create or update resources in Sendook — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sendook environment.
Creating an inbox is a reversible write operation that establishes a new email management resource. While the tool description is empty, the naming convention and server context clearly indicate inbox creation. This is categorized as Write rather than Execute because it performs a specific data creation action rather than executing arbitrary code.
From the tool's definition Tool name 'sendook_create_inbox' indicates creation of a new inbox resource. Server description states the platform 'Enables AI agents to send and receive emails, manage inboxes, threads, and webhooks programmatically.' The 'create' prefix combined with inbox…
Attacks that exploit this kind of access
sendook_create_inbox. It is categorised as a Write tool in the Sendook MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sendook MCP server in PolicyLayer and add a rule for sendook_create_inbox: 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 Sendook. Nothing to install.
sendook_create_inbox 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 sendook_create_inbox 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 sendook_create_inbox. 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.
sendook_create_inbox is provided by the Sendook MCP server (streamlinedstartup/sendook-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 →