Navigate to and show a list, project, area, tag, or to-do in Things. Built-in list IDs: inbox, today, anytime, upcoming, someday, logbook, tomorrow, deadlines, repeating, all-projects, logged-projects.
AI agents invoke show to trigger actions in Things App MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs a UI action (navigating/displaying a view) in an external application via the Things URL scheme or AppleScript. It doesn't read data back to the agent, write/modify data, or destroy anything — it triggers an external operation in the app. Execute is the most appropriate category since it causes a side effect (changing the application's UI state), even though the blast radius is very low.
From the tool's definition 'Navigate to and show a list, project, area, tag, or to-do in Things' — triggers a UI navigation action in the Things app, an external operation beyond simple data retrieval
Attacks that exploit this kind of access
Navigate to and show a list, project, area, tag, or to-do in Things. Built-in list IDs: inbox, today, anytime, upcoming, someday, logbook, tomorrow, deadlines, repeating, all-projects, logged-projects. It is categorised as a Execute tool in the Things App MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Things App MCP server in PolicyLayer and add a rule for show: 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.
show is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the show 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 show. 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.
show 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 →