Low Risk

get_random_inbox

Get a random sample of todos from Inbox.

How to control get_random_inbox ↓

AI agents call get_random_inbox to retrieve information from Things 3 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and returns data (a random sample of todos) from the Inbox without creating, modifying, deleting, or executing any external operations. It is a read-only retrieval operation with no side effects on the task management system.

From the tool's definition Tool name 'get_random_inbox' and description 'Get a random sample of todos from Inbox' indicate a retrieval operation with no modification or deletion of data.

Documented attack patterns abuse exactly the kind of access get_random_inbox gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Things 3 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_random_inbox:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_random_inbox": {}
  }
}

get_random_inbox is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Things 3 MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_random_inbox tool do? +

Get a random sample of todos from Inbox. It is categorised as a Read tool in the Things 3 MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_random_inbox? +

Register the Things 3 MCP Server MCP server in PolicyLayer and add a rule for get_random_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 3 MCP Server. Nothing to install.

What risk level is get_random_inbox? +

get_random_inbox is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_random_inbox? +

Yes. Add a rate_limit block to the get_random_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 get_random_inbox completely? +

Set action: deny in the PolicyLayer policy for get_random_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 get_random_inbox? +

get_random_inbox is provided by the Things 3 MCP Server MCP server (rossshannon/things3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Things 3 MCP Server tool call.

Deterministic rules across all 24 Things 3 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

24 Things 3 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.