Capture a new inbox item in Tududi
AI agents use create_inbox_item to create or update resources in Tududi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tududi MCP Server environment.
This tool creates new data (an inbox item) in the Tududi system, which is reversible—inbox items can be edited, moved, or deleted. It does not execute external code, trigger financial transactions, or permanently destroy data. The blast radius of misuse is low, as inbox items are transient working-memory artifacts in GTD methodology. Classification as Write is appropriate.
From the tool's definition Tool name 'create_inbox_item' and description 'Capture a new inbox item' indicate data creation. 'Inbox item' in GTD contexts is a temporary, easily-modifiable entry point for tasks/notes that can be reviewed and organized later.
Attacks that exploit this kind of access
Capture a new inbox item in Tududi. It is categorised as a Write tool in the Tududi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tududi MCP Server MCP server in PolicyLayer and add a rule for create_inbox_item: 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 Tududi MCP Server. Nothing to install.
create_inbox_item 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 create_inbox_item 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 create_inbox_item. 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.
create_inbox_item is provided by the Tududi MCP Server MCP server (jeanbispo/tududi-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 →