build_local_report
Build a local JSON or Markdown report from tasks, plans, runs, and verification evidence without hosted analytics.
This record as markdown: /tools/todos/build-local-report.md
What build_local_report does on Todos
AI agents call build_local_report to retrieve information from Todos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why build_local_report is rated Low
This tool reads existing task data and generates a report (JSON or Markdown). It queries/retrieves data and produces a local output file with no side effects on external systems. No data is modified, deleted, or transmitted externally.
From the tool's definition Build a local JSON or Markdown report from tasks, plans, runs, and verification evidence without hosted analytics
Attacks that exploit this kind of access
The rule that runs build_local_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For build_local_report, this is the rule to start with:
build_local_report 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 Todos, apply this rule, and every build_local_report call is checked against it from then on.
Questions about build_local_report
Build a local JSON or Markdown report from tasks, plans, runs, and verification evidence without hosted analytics. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.
Register the Todos MCP server in PolicyLayer and add a rule for build_local_report: 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 Todos. Nothing to install.
build_local_report 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 build_local_report 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 build_local_report. 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.
build_local_report is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todos, and thousands of servers like it.
This server
Across the catalogue