Low Risk

freeze_card

Temporarily freeze a card. The card cannot be used for purchases while frozen. Use unfreeze_card to re-enable it. This is reversible (unlike closing a card).

Part of the ASG Card server.

freeze_card is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE ASG CARD →

Free to start. No card required.

AI agents call freeze_card to retrieve information from ASG Card without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though freeze_card only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "freeze_card": {}
  }
}

See the full ASG Card policy for all 18 tools.

Get this rule live on your own ASG Card server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ASG CARD →

View all 18 tools →

These attack patterns abuse exactly the kind of access freeze_card gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so freeze_card only ever does what you allow.

SECURE ASG CARD →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the freeze_card tool do? +

Temporarily freeze a card. The card cannot be used for purchases while frozen. Use unfreeze_card to re-enable it. This is reversible (unlike closing a card).. It is categorised as a Read tool in the ASG Card MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on freeze_card? +

Register the ASG Card MCP server in PolicyLayer and add a rule for freeze_card: 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 ASG Card. Nothing to install.

What risk level is freeze_card? +

freeze_card is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit freeze_card? +

Yes. Add a rate_limit block to the freeze_card 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 freeze_card completely? +

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

freeze_card is provided by the ASG Card MCP server (@asgcard/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ASG Card tool call.

Deterministic rules across all 18 ASG Card tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.