AI agents use save_search_view to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
This tool persists a search view (a reversible configuration/preference), which is a Write operation. It does not execute arbitrary code, delete data irreversibly, move money, or read sensitive data in bulk — it merely saves a filtered view definition. Severity is low because the blast radius of an AI misusing this is limited to creating unwanted saved searches, which are trivial to clean up.
From the tool's definition Tool name contains 'save' and description states 'Save a local search view' — creates or stores a search view configuration locally without deleting or modifying existing tasks/data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Save a local search view for tasks, projects, plans, runs, comments, or all records. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for save_search_view: 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.
save_search_view is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_search_view 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 save_search_view. 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.
save_search_view 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.
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 →