Replace a Brighty card
AI agents use brighty_set_card_limits to commit financial operations through Brighty MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool operates on a Brighty payment card. Even though the description says 'Replace a Brighty card', in the context of a banking/financial MCP server that issues cards, setting card limits directly affects financial controls and spending capacity. Modifying card limits could enable or restrict financial transactions, placing it in the Financial category.
From the tool's definition 'Replace a Brighty card' on a banking infrastructure server that issues cards and handles payments
Attacks that exploit this kind of access
Replace a Brighty card. It is categorised as a Financial tool in the Brighty MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Brighty MCP Server MCP server in PolicyLayer and add a rule for brighty_set_card_limits: 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_set_card_limits is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the brighty_set_card_limits 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_set_card_limits. 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_set_card_limits 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 →