validate_policy_pack
Validate a task against a local policy pack (done gates). Use dry_run to explain without blocking.
This record as markdown: /tools/todos/validate-policy-pack.md
What validate_policy_pack does on Todos
AI agents call validate_policy_pack 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 validate_policy_pack is rated Low
The tool validates/checks a task against policy rules. The 'dry_run' option and 'without blocking' language indicate it reads and evaluates state without modifying anything. This is a read/query operation that returns a validation result.
From the tool's definition Validate a task against a local policy pack (done gates). Use dry_run to explain without blocking.
Attacks that exploit this kind of access
The rule that runs validate_policy_pack 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 validate_policy_pack, this is the rule to start with:
validate_policy_pack 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 validate_policy_pack call is checked against it from then on.
Questions about validate_policy_pack
Validate a task against a local policy pack (done gates). Use dry_run to explain without blocking. 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 validate_policy_pack: 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.
validate_policy_pack 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 validate_policy_pack 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 validate_policy_pack. 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.
validate_policy_pack 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