true_credit_cost · Axiom Calculator MCP: Risk & Policy

WHAT IT DOES

What true_credit_cost does on Axiom Calculator

AI agents use true_credit_cost 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.

WHY IT NEEDS A POLICY

Why true_credit_cost needs a policy

An AI agent can call true_credit_cost 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

Recommended rule Ready

Verdict

true_credit_cost Rate-limited

true_credit_cost stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "true_credit_cost": {
      "limits": [
        {
          "counter": "true_credit_cost_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Axiom Calculator, so you can run agents against it safely.

FAQ

Questions about true_credit_cost

What does the true_credit_cost tool do? +

true_credit_cost. 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.

How do I enforce a policy on true_credit_cost? +

Register the Axiom Calculator MCP server in PolicyLayer and add a rule for true_credit_cost: 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.

What risk level is true_credit_cost? +

true_credit_cost is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit true_credit_cost? +

Yes. Add a rate_limit block to the true_credit_cost 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.

How do I block true_credit_cost completely? +

Set action: deny in the PolicyLayer policy for true_credit_cost. 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.

What MCP server provides true_credit_cost? +

true_credit_cost 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.