AI agents call find_hotspots to retrieve information from Orihime without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'find_hotspots' tool appears designed to identify performance hotspots in code, consistent with the server's stated capability to expose tools for 'performance hotspot' analysis. This is a query/search operation against the indexed code knowledge graph, retrieving information without side effects.
From the tool's definition Tool name 'find_hotspots' suggests querying or locating performance bottlenecks within a code graph; sibling tools are predominantly Read operations (find_callees, find_callers, find_entry_points, etc.) that traverse the embedded KuzuDB without modification.
Attacks that exploit this kind of access
find_hotspots. It is categorised as a Read tool in the Orihime MCP Server, which means it retrieves data without modifying state.
Register the Orihime MCP server in PolicyLayer and add a rule for find_hotspots: 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 Orihime. Nothing to install.
find_hotspots 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 find_hotspots 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 find_hotspots. 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.
find_hotspots is provided by the Orihime MCP server (srinivasan-sundaresan95/orihime). 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 →