mark_inbox_done · Jikan MCP: Risk & Policy

WHAT IT DOES

What mark_inbox_done does on Jikan

AI agents use mark_inbox_done 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 mark_inbox_done needs a policy

The tool appears to update the status of inbox items (likely setting a 'done' flag), which is a reversible modification. This qualifies as Write rather than Destructive since marking done does not irreversibly delete data. Severity is medium because misuse could cause workflow confusion if items are incorrectly marked complete, but the operation is reversible via uncompleting or other corrections.

From the tool's definition Tool name 'mark_inbox_done' suggests marking an inbox item as complete/done, which modifies state reversibly. Server context indicates it manages behavioral tracking sessions and todo items.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_inbox_done Rate-limited

mark_inbox_done 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": {
    "mark_inbox_done": {
      "limits": [
        {
          "counter": "mark_inbox_done_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 mark_inbox_done

What does the mark_inbox_done tool do? +

mark_inbox_done. 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 mark_inbox_done? +

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

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

Can I rate-limit mark_inbox_done? +

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

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

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