Get full context for a specific file, including all its symbols.
AI agents call axon_pro_file_context to retrieve information from Axon Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structural information about a file (symbols, context) from a knowledge graph. It performs a read-only query against codebase analysis data. There are no side effects, no code execution, no data modification, and no destructive operations. The blast radius of misuse is minimal—an agent could only over-query or access files it shouldn't, but cannot alter code or trigger external actions.
From the tool's definition Tool name 'axon_pro_file_context' and description 'Get full context for a specific file, including all its symbols' indicate a retrieval operation that queries codebase metadata without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access axon_pro_file_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Axon Pro, and nothing reaches the server without passing your rules. This is the rule we recommend for axon_pro_file_context:
{
"version": "1",
"default": "deny",
"tools": {
"axon_pro_file_context": {}
}
}axon_pro_file_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get full context for a specific file, including all its symbols. It is categorised as a Read tool in the Axon Pro MCP Server, which means it retrieves data without modifying state.
Register the Axon Pro MCP server in PolicyLayer and add a rule for axon_pro_file_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 Axon Pro. Nothing to install.
axon_pro_file_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 axon_pro_file_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 axon_pro_file_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.
axon_pro_file_context is provided by the Axon Pro MCP server (talhamsajid/axon-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Axon Pro tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Axon Pro tools catalogued and risk-classified — across an index of 42,500+ MCP servers.