Сравнивает реализацию символа в двух файлах через diff
AI agents call compare_symbols to retrieve information from Booster MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a semantic diff operation on code symbols across files. It retrieves and compares existing data without modifying, executing, or deleting anything. This is purely informational analysis, consistent with other Read category tools on the server like 'code_grep' and 'find_symbol'. The operation has no side effects on the codebase.
From the tool's definition Tool description: 'Сравнивает реализацию символа в двух файлах через diff' (Compares the implementation of a symbol in two files via diff). This is a comparison/analysis operation that retrieves and displays differences between code symbols.
Attacks that exploit this kind of access
Сравнивает реализацию символа в двух файлах через diff. It is categorised as a Read tool in the Booster MCP MCP Server, which means it retrieves data without modifying state.
Register the Booster MCP server in PolicyLayer and add a rule for compare_symbols: 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 Booster MCP. Nothing to install.
compare_symbols 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 compare_symbols 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 compare_symbols. 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.
compare_symbols is provided by the Booster MCP server (neuroghostdev/booster_mcp). 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 →