AI agents call get_path_context to retrieve information from Axiom-hub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly indicates a read/query operation with no side effects. Within the context of a decision memory and architectural consistency system, 'get_path_context' likely retrieves context about a file or code path—a non-destructive data retrieval.
From the tool's definition Tool name 'get_path_context' suggests a retrieval operation ('get'). Description is empty, limiting direct evidence, but the naming convention aligns with sibling read tools like 'get_board_items', 'get_decision_timeline', and 'get_project_context'.
Attacks that exploit this kind of access
get_path_context. It is categorised as a Read tool in the Axiom-hub MCP Server, which means it retrieves data without modifying state.
Register the Axiom-hub MCP server in PolicyLayer and add a rule for get_path_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 Axiom-hub. Nothing to install.
get_path_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_path_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_path_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_path_context is provided by the Axiom-hub MCP server (varunajaytawde28-design/smm-sync). 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 →