AI agents call find_usages to retrieve information from MCP-TY without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads/queries the codebase to locate references to a given symbol. It performs no writes, executions, or deletions — purely a read/search operation with no side effects.
From the tool's definition Find all references to symbol at position
Attacks that exploit this kind of access
Find all references to symbol at position (1-based). It is categorised as a Read tool in the MCP-TY MCP Server, which means it retrieves data without modifying state.
Register the MCP-TY MCP server in PolicyLayer and add a rule for find_usages: 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 MCP-TY. Nothing to install.
find_usages 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_usages 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_usages. 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_usages is provided by the MCP-TY MCP server (qinsehm1128/mcp-ty). 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 →