List inbox capture items with optional pagination and status details
AI agents call list_inbox to retrieve information from Tududi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves inbox items from the Tududi productivity platform. It performs no modifications, deletions, or external actions. The pagination and status details are read-only metadata. Listing inbox items has minimal blast radius if misused by an AI agent, as it only exposes existing data without altering state or triggering external operations.
From the tool's definition Tool name 'list_inbox' and description 'List inbox capture items with optional pagination and status details' indicate a retrieval operation with no side effects. The verb 'list' is a classic Read operation pattern.
Attacks that exploit this kind of access
List inbox capture items with optional pagination and status details. It is categorised as a Read tool in the Tududi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tududi MCP Server MCP server in PolicyLayer and add a rule for list_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 Tududi MCP Server. Nothing to install.
list_inbox is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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 list_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.
list_inbox 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 →