get_run_logs

Retrieve append-only log entries for a specific Agent run. Agents write logs during execution to record progress, tool calls, decisions, and errors. Supports incremental polling with since_id.

SERVERTodo for AI MCP Server SOURCEtodo-for-ai/todo-for-ai-mcp

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/todo-for-ai-todo-for-ai-mcp/get-run-logs.md

WHAT IT DOES

What get_run_logs does on Todo for AI MCP Server

AI agents call get_run_logs to retrieve information from Todo for AI MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_run_logs is rated Low

Even though get_run_logs 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 get_run_logs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Todo for AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_run_logs, this is the rule to start with:

get_run_logs Allowed

get_run_logs 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": {
    "get_run_logs": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Todo for AI MCP Server, apply this rule, and every get_run_logs call is checked against it from then on.

FAQ

Questions about get_run_logs

What does the get_run_logs tool do? +

Retrieve append-only log entries for a specific Agent run. Agents write logs during execution to record progress, tool calls, decisions, and errors. Supports incremental polling with since_id. It is categorised as a Read tool in the Todo for AI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_run_logs? +

Register the Todo for AI MCP Server MCP server in PolicyLayer and add a rule for get_run_logs: 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 Todo for AI MCP Server. Nothing to install.

What risk level is get_run_logs? +

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

Can I rate-limit get_run_logs? +

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

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

get_run_logs is provided by the Todo for AI MCP Server MCP server (todo-for-ai/todo-for-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Todo for AI MCP Server, and thousands of servers like it.

This server

All 244 Todo for AI MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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