Unfreeze a previously frozen Brighty card so authorisations can resume. Has no effect on cards that are not in FROZEN status; check brighty_get_card first when in doubt.
AI agents use brighty_unfreeze_card to create or update resources in Brighty MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Brighty MCP Server environment.
Unfreezing a card re-enables financial transactions on it. This is a reversible state change (the card can be re-frozen), so it's Write rather than Destructive. However, the blast radius is high because re-enabling a card allows new payments and authorisations to proceed, which could have significant financial consequences if misused by an AI agent.
From the tool's definition Unfreeze a previously frozen Brighty card so authorisations can resume
Attacks that exploit this kind of access
Unfreeze a previously frozen Brighty card so authorisations can resume. Has no effect on cards that are not in FROZEN status; check brighty_get_card first when in doubt. It is categorised as a Write tool in the Brighty MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Brighty MCP Server MCP server in PolicyLayer and add a rule for brighty_unfreeze_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 Brighty MCP Server. Nothing to install.
brighty_unfreeze_card 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 brighty_unfreeze_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.
Set action: deny in the PolicyLayer policy for brighty_unfreeze_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.
brighty_unfreeze_card is provided by the Brighty MCP Server MCP server (razz-team/brighty-agent-toolkit). 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 →