AI agents call get_file_location 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.
This tool queries a code knowledge graph to retrieve file paths and line numbers—pure information retrieval with no side effects, no execution, no data modification, and no destructive operations. It is a straightforward Read operation typical of code indexing and analysis tools.
From the tool's definition Tool name 'get_file_location' and description 'Get the source file path and line number for a method or class by FQN' indicate retrieval of metadata about code locations without modification.
Attacks that exploit this kind of access
Get the source file path and line number for a method or class by FQN. 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 get_file_location: 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.
get_file_location 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_file_location 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_file_location. 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_file_location 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 →