List the card designs available to the authenticated business. Each design
AI agents call brighty_list_card_designs 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 tool queries and returns a list of available card designs for the authenticated business. It performs no modification, deletion, execution, or financial transaction. While it operates within a banking infrastructure server, the tool itself is purely informational—listing available design options.
From the tool's definition Tool name 'brighty_list_card_designs' and description 'List the card designs available' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List the card designs available to the authenticated business. Each design. 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_list_card_designs: 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_list_card_designs 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_list_card_designs 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_list_card_designs. 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_list_card_designs 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 →