AI agents use send_inbox 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.
Based on the server's purpose (behavioral session tracking and activity management) and the pattern of sibling tools, 'send_inbox' most likely creates or adds an item to an inbox—a reversible write operation. Without explicit documentation, confidence is moderate (0.65).
From the tool's definition Tool name 'send_inbox' suggests creating or posting a message/item to an inbox. The description is empty, but sibling tools on this server include 'archive_inbox', 'create_todo', 'create_activity', 'create_past_session', and 'complete_todo', all of which are…
Attacks that exploit this kind of access
send_inbox. 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.
Register the Jikan MCP server in PolicyLayer and add a rule for send_inbox: 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.
send_inbox is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_inbox 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.
Set action: deny in the PolicyLayer policy for send_inbox. 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.
send_inbox 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.
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 →