New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

create_inbox

Create a new email inbox. Returns the inbox details including the email address.

SERVERPypi:deadsimple Email SOURCEpypi:deadsimple-email
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/deadsimple-email/create-inbox.md

What create_inbox does on Pypi:deadsimple Email

AI agents use create_inbox to create or update resources in Pypi:deadsimple Email, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pypi:deadsimple Email environment.

Why create_inbox is rated Medium

This tool creates a new email inbox, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. The severity is medium because an agent misusing this could create many inboxes (resource exhaustion, potential cost implications if inboxes are metered), but the action is not inherently destructive or financial in nature.

From the tool's definition Tool description states 'Create a new email inbox' — a creation operation that modifies state by adding a new resource to the system.

Questions about create_inbox

What does the create_inbox tool do? +

Create a new email inbox. Returns the inbox details including the email address. It is categorised as a Write tool in the Pypi:deadsimple Email MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_inbox? +

Register the Pypi:deadsimple Email MCP server in PolicyLayer and add a rule for 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 Pypi:deadsimple Email. Nothing to install.

What risk level is create_inbox? +

create_inbox is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_inbox? +

Yes. Add a rate_limit block to the 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.

How do I block create_inbox completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides create_inbox? +

create_inbox is provided by the Pypi:deadsimple Email MCP server (pypi:deadsimple-email). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Pypi:deadsimple Email, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Pypi:deadsimple Email's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.