Low Risk

get_symbol_usages

get_symbol_usages

How to control get_symbol_usages ↓

AI agents call get_symbol_usages to retrieve information from Search Tools MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves data about where symbols are used in code repositories—a read-only operation with no side effects. It supports the server's core purpose of code analysis and dependency tracing. Even though the description is empty, the naming convention and context of sibling tools strongly suggest a query/retrieval function rather than a write, execute, or destructive operation.

From the tool's definition Tool name 'get_symbol_usages' indicates retrieval of symbol usage information. The server description emphasizes 'search' and 'identify' operations without mentioning modification or deletion. All sibling tools are analytical (analyze_*, *_analysis, search).

Documented attack patterns abuse exactly the kind of access get_symbol_usages gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Search Tools MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_symbol_usages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_symbol_usages": {}
  }
}

get_symbol_usages is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Search Tools MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_symbol_usages tool do? +

get_symbol_usages. It is categorised as a Read tool in the Search Tools MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_symbol_usages? +

Register the Search Tools MCP Server MCP server in PolicyLayer and add a rule for get_symbol_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 Search Tools MCP Server. Nothing to install.

What risk level is get_symbol_usages? +

get_symbol_usages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_symbol_usages? +

Yes. Add a rate_limit block to the get_symbol_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.

How do I block get_symbol_usages completely? +

Set action: deny in the PolicyLayer policy for get_symbol_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.

What MCP server provides get_symbol_usages? +

get_symbol_usages is provided by the Search Tools MCP Server MCP server (voxmenthe/search-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Search Tools MCP Server tool call.

Deterministic rules across all 21 Search Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

21 Search Tools MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.