AI agents call get_emotion_sessions 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.
This tool queries and retrieves historical session data without modifying, deleting, or executing any operations. It is a straightforward data retrieval endpoint that returns session information including duration and event count. The low severity reflects that misuse would only expose existing data rather than cause destructive changes or financial impact.
From the tool's definition Tool name and description indicate it 'List[s] past interaction sessions' — a retrieval operation with 'No decryption required.' The verb 'List' and absence of side effects (create, modify, delete) confirm read-only behavior.
Attacks that exploit this kind of access
List past interaction sessions with duration and event count. No decryption required. It is categorised as a Read tool in the Jikan MCP Server, which means it retrieves data without modifying state.
Register the Jikan MCP server in PolicyLayer and add a rule for get_emotion_sessions: 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.
get_emotion_sessions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_emotion_sessions 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 get_emotion_sessions. 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.
get_emotion_sessions 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 →