List tasks in the Inbox — tasks not yet scheduled or assigned to a list.
AI agents call list_inbox to retrieve information from Things Cloud MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries task data from the Inbox without creating, modifying, deleting, or executing any operations. It has no side effects and falls squarely into the Read category. The low severity reflects minimal blast radius—an AI agent misusing this would only retrieve task information, not alter or delete anything. Confidence is high due to clear evidence in both the tool name and description.
From the tool's definition Tool name 'list_inbox' and description 'List tasks in the Inbox' indicate a retrieval operation with no modifications. The verb 'List' is explicitly a read operation that queries existing data without side effects.
Attacks that exploit this kind of access
List tasks in the Inbox — tasks not yet scheduled or assigned to a list. It is categorised as a Read tool in the Things Cloud MCP MCP Server, which means it retrieves data without modifying state.
Register the Things Cloud 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 Things Cloud MCP. 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 Things Cloud MCP server (nkootstra/things). 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 →