mark_inbox_seen_bulk · Jikan MCP: Risk & Policy

WHAT IT DOES

What mark_inbox_seen_bulk does on Jikan

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

The tool modifies data (message read status) reversibly rather than retrieving it (Read), executing arbitrary operations (Execute), or permanently deleting data (Destructive). Bulk operations do not elevate the severity since marking messages as seen is a benign metadata update with no side effects beyond the intended state change. Low severity reflects minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'mark_inbox_seen_bulk' indicates modification of message state (marking as seen), and description states it marks 'multiple inbox messages as seen'. This is a state change operation that is reversible (messages can be marked unseen again).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_inbox_seen_bulk Rate-limited

mark_inbox_seen_bulk 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_seen_bulk": {
      "limits": [
        {
          "counter": "mark_inbox_seen_bulk_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_seen_bulk

What does the mark_inbox_seen_bulk tool do? +

Mark multiple inbox messages as seen in one call. Free (0 credits). 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_seen_bulk? +

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

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

Can I rate-limit mark_inbox_seen_bulk? +

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

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

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