request_input

Request deterministic clarification.

SERVERTodos SOURCE@hasna/todos

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/todos/request-input.md

WHAT IT DOES

What request_input does on Todos

AI agents call request_input 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.

RISK

Why request_input is rated Low

Even though request_input only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

request_input Allowed

request_input is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_input": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about request_input

What does the request_input tool do? +

Request deterministic clarification. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on request_input? +

Register the Todos MCP server in PolicyLayer and add a rule for request_input: 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 request_input? +

request_input is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit request_input? +

Yes. Add a rate_limit block to the request_input 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 request_input completely? +

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

request_input 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 →

Across the catalogue

get_example_input on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →