run_saved_view

Execute a saved view by slug or id.

SERVERTodos SOURCE@hasna/todos

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/todos/run-saved-view.md

WHAT IT DOES

What run_saved_view does on Todos

AI agents invoke run_saved_view to trigger actions in Todos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why run_saved_view is rated High

The tool executes a saved view, which could retrieve or process data based on stored parameters. While 'saved view' typically suggests read-only query execution (similar to a SQL view), the use of 'Execute' in the description and 'run' in the name suggests active invocation of logic rather than simple retrieval.

From the tool's definition Tool name contains 'run' and description states 'Execute a saved view' - indicates execution of a predefined query or operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_saved_view 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 run_saved_view, this is the rule to start with:

run_saved_view Rate-limited

run_saved_view stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_saved_view": {
      "limits": [
        {
          "counter": "run_saved_view_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every run_saved_view call is checked against it from then on.

FAQ

Questions about run_saved_view

What does the run_saved_view tool do? +

Execute a saved view by slug or id. It is categorised as a Execute tool in the Todos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_saved_view? +

Register the Todos MCP server in PolicyLayer and add a rule for run_saved_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.

What risk level is run_saved_view? +

run_saved_view is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_saved_view? +

Yes. Add a rate_limit block to the run_saved_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.

How do I block run_saved_view completely? +

Set action: deny in the PolicyLayer policy for run_saved_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.

What MCP server provides run_saved_view? +

run_saved_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.

KEEP EXPLORING

More on Todos, and thousands of servers like it.

This server

All 528 Todos tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →