complete_todo_with_session · Jikan MCP: Risk & Policy

WHAT IT DOES

What complete_todo_with_session does on Jikan

AI agents use complete_todo_with_session to create or update resources in Jikan — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jikan environment.

WHY IT NEEDS A POLICY

Why complete_todo_with_session needs a policy

This tool appears to mark a todo item as complete and associate it with a session, modifying state reversibly. It aligns with the Write category (updates data). Severity is medium because completing todos could affect workflows, but changes are reversible via other tools. Confidence is lowered from 0.85 to 0.7 due to empty description limiting verification of exact behavior.

From the tool's definition Tool name 'complete_todo_with_session' indicates modification of todo state (marking as complete). Server context involves 'session management' and related tools like 'complete_todo' and 'create_past_session' that create or modify data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_todo_with_session Rate-limited

complete_todo_with_session stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "complete_todo_with_session": {
      "limits": [
        {
          "counter": "complete_todo_with_session_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Jikan, so you can run agents against it safely.

FAQ

Questions about complete_todo_with_session

What does the complete_todo_with_session tool do? +

complete_todo_with_session. It is categorised as a Write tool in the Jikan MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on complete_todo_with_session? +

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

complete_todo_with_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit complete_todo_with_session? +

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

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

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