todo_history

List fully completed todos with pagination. Free (0 credits).

Server Jikan thunderrabbit/jikan
Category Read
Risk class Low
Parameters 00 required

What todo_history does on Jikan

AI agents call todo_history to retrieve information from Jikan without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why todo_history needs a policy

This tool queries and retrieves historical todo data in a paginated format. It does not create, modify, delete, or execute any operations. The 'list' verb and 'Free (0 credits)' designation confirm this is a non-destructive read-only query operation. Blast radius is minimal as it only accesses past completion records.

From the tool's definition Tool name 'todo_history' and description 'List fully completed todos with pagination' indicate a retrieval operation with no side effects.

Questions about todo_history

What does the todo_history tool do? +

List fully completed todos with pagination. Free (0 credits). It is categorised as a Read tool in the Jikan MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on todo_history? +

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

What risk level is todo_history? +

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

Can I rate-limit todo_history? +

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

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

todo_history is provided by the Jikan MCP server (thunderrabbit/jikan). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.