This record as markdown: /tools/todos/list-search-views.md
What list_search_views does on Todos
AI agents call list_search_views 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 list_search_views is rated Low
This tool retrieves metadata about saved search views with no side effects. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could only discover what search views exist locally, which poses negligible security risk.
From the tool's definition Tool name 'list_search_views' and description 'List local saved search views' indicate a read-only operation that retrieves and displays existing search view configurations without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
The rule that runs list_search_views 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 list_search_views, this is the rule to start with:
list_search_views 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 list_search_views call is checked against it from then on.
Questions about list_search_views
List local saved search views. 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 list_search_views: 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.
list_search_views 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 list_search_views 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 list_search_views. 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.
list_search_views 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