Get a specific to-do by its ID. Uses AppleScript/JXA (macOS only).
AI agents call get-todo-by-id to retrieve information from Things App MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a single to-do item by identifier without modifying, deleting, or executing external operations. It is a straightforward read operation with minimal blast radius—the worst an AI agent could do is retrieve task data it shouldn't see, but no data is modified, deleted, or executed. Severity is low because it only affects information disclosure risk.
From the tool's definition Tool name 'get-todo-by-id' and description 'Get a specific to-do by its ID' indicate a retrieval operation. The mechanism uses 'AppleScript/JXA (macOS only)' for querying, which is read-only access to task data.
Attacks that exploit this kind of access
Get a specific to-do by its ID. Uses AppleScript/JXA (macOS only). It is categorised as a Read tool in the Things App MCP MCP Server, which means it retrieves data without modifying state.
Register the Things App MCP server in PolicyLayer and add a rule for get-todo-by-id: 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 App MCP. Nothing to install.
get-todo-by-id 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 get-todo-by-id 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 get-todo-by-id. 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.
get-todo-by-id is provided by the Things App MCP server (lucas-flatwhite/things-app-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 →