Get a symbol's definition with surrounding context lines from the source file.
AI agents call get_symbol_context to retrieve information from Unreal Source without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries indexed source code to retrieve definitional information and context. It has no side effects—it does not modify code, execute operations, or delete data. The worst case misuse is excessive queries consuming resources, which presents low risk. Classified as Read with low severity.
From the tool's definition Tool retrieves a symbol's definition with surrounding context lines from source files. The description uses 'Get' and 'read' semantics with no modification or execution.
Attacks that exploit this kind of access
Get a symbol's definition with surrounding context lines from the source file. It is categorised as a Read tool in the Unreal Source MCP Server, which means it retrieves data without modifying state.
Register the Unreal Source MCP server in PolicyLayer and add a rule for get_symbol_context: 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 Unreal Source. Nothing to install.
get_symbol_context 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_symbol_context 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_symbol_context. 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_symbol_context is provided by the Unreal Source MCP server (tumourlove/deprecated-unreal-source-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 →