compound_interest
AI agents use compound_interest to create or update resources in Axiom Calculator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Axiom Calculator environment.
An AI agent can call compound_interest faster than any human can review — one bad instruction and it creates or modifies resources in Axiom Calculator by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
compound_interest. It is categorised as a Write tool in the Axiom Calculator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Axiom Calculator MCP server in PolicyLayer and add a rule for compound_interest: 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 Calculator. Nothing to install.
compound_interest is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the compound_interest 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 compound_interest. 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.
compound_interest is provided by the Axiom Calculator MCP server (vdalhambra/axiom-calculator-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 →