AI agents call get_decision_timeline 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 tool retrieves a timeline of prior decisions from persistent memory—a read-only query operation with no side effects. Even if misused, an AI agent accessing historical decisions poses minimal risk compared to tools that create (add_decision), check for conflicts (check_contradictions), or claim resources (claim_file). Classification as Read is supported by consistent naming patterns in the tool suite.
From the tool's definition Tool name 'get_decision_timeline' indicates retrieval/query operation with no state mutation. Server context shows this is a decision memory system where tools like 'add_decision' modify state while 'get_*' variants (get_board_items, get_compliance_lineage,…
Attacks that exploit this kind of access
get_decision_timeline. 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_decision_timeline: 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_decision_timeline 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_decision_timeline 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_decision_timeline. 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_decision_timeline 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 →