Fetch the virtual card product configuration: per-condition fees (issueFee, deliveryFee), free/total card limits, supported form factors and card types. Call this before brighty_order_card so the user can see what
AI agents call brighty_get_virtual_card_product 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 retrieves configuration metadata (fees, limits, supported types) about virtual card products. It performs a query operation with no ability to modify, delete, execute code, or transfer funds. The description is cut off mid-sentence but the operative verb is clearly 'Fetch,' indicating data retrieval only.
From the tool's definition Tool name contains 'get' and description states 'Fetch the virtual card product configuration' with details about fees, limits, and form factors—all read operations with no side effects.
Attacks that exploit this kind of access
Fetch the virtual card product configuration: per-condition fees (issueFee, deliveryFee), free/total card limits, supported form factors and card types. Call this before brighty_order_card so the user can see what. 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_virtual_card_product: 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_virtual_card_product 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_virtual_card_product 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_virtual_card_product. 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_virtual_card_product 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 →