Fetch a single Brighty card by id, including its kind, status, last4, attached accountId, currency, design, cardholder name, and current limits.
AI agents call brighty_get_card to retrieve information from Brighty MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only retrieval operation that queries card information. While the context (banking infrastructure) suggests sensitive financial data, the tool itself performs no write, execute, destructive, or financial operations—it only retrieves and displays existing card metadata.
From the tool's definition Tool fetches card details (kind, status, last4, accountId, currency, design, cardholder name, limits) without modification; returns data only.
Attacks that exploit this kind of access
Fetch a single Brighty card by id, including its kind, status, last4, attached accountId, currency, design, cardholder name, and current limits. It is categorised as a Read tool in the Brighty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Brighty MCP Server MCP server in PolicyLayer and add a rule for brighty_get_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_get_card is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the brighty_get_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_get_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_get_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 →