get_todo
Get ONE of YOUR to-dos by id — its full row. Owner-scoped: an id you don't own returns not-found (never reveals another user's to-do). Returns { todo }.
This record as markdown: /tools/dev-busymate-busymate-devtools/get-todo.md
What get_todo does on Busymate DevTools
AI agents call get_todo to retrieve information from Busymate DevTools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | The to-do's uuid (from list_todos). |
Parameters from the server's own tool schema.
Why get_todo is rated Low
This is a simple data retrieval operation that fetches a single to-do item belonging to the authenticated user. It has no side effects, cannot modify or delete data, and includes proper access controls. The 'get_' prefix and retrieval-only semantics confirm Read category. Severity is low because exposure is limited to the user's own to-do items with no blast radius beyond personal data access.
From the tool's definition Tool name 'get_todo' and description states it retrieves 'ONE of YOUR to-dos by id — its full row' with owner-scoped access control that prevents cross-user access ('an id you don't own returns not-found').
Attacks that exploit this kind of access
The rule that runs get_todo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Busymate DevTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_todo, this is the rule to start with:
get_todo is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Busymate DevTools, apply this rule, and every get_todo call is checked against it from then on.
Questions about get_todo
Get ONE of YOUR to-dos by id — its full row. Owner-scoped: an id you don't own returns not-found (never reveals another user's to-do). Returns { todo }. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
get_todo accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools MCP server in PolicyLayer and add a rule for get_todo: 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 Busymate DevTools. Nothing to install.
get_todo 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 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. 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 is provided by the Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue