export_verification_evidence
Export portable verification evidence bundle for a task or run record.
This record as markdown: /tools/todos/export-verification-evidence.md
What export_verification_evidence does on Todos
AI agents call export_verification_evidence 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 export_verification_evidence is rated Low
The tool exports/reads existing verification evidence data from a task or run record. 'Export' indicates retrieval of data for portability, with no indication of modification, deletion, or execution of code. This is fundamentally a read/fetch operation.
From the tool's definition Export portable verification evidence bundle for a task or run record
Attacks that exploit this kind of access
The rule that runs export_verification_evidence 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 export_verification_evidence, this is the rule to start with:
export_verification_evidence 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 export_verification_evidence call is checked against it from then on.
Questions about export_verification_evidence
Export portable verification evidence bundle for a task or run record. 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 export_verification_evidence: 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.
export_verification_evidence 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 export_verification_evidence 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 export_verification_evidence. 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.
export_verification_evidence 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