Get card profile/details by card account ID
AI agents call pex_get_card to retrieve information from PEX 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 card profile and details information by querying with a card account ID. It performs no data modification, deletion, financial transactions, code execution, or side effects. While the PEX Card system involves financial accounts, this particular tool only reads/queries existing card details, making it a standard Read operation with low risk if misused by an AI agent.
From the tool's definition Tool name 'pex_get_card' and description 'Get card profile/details by card account ID' indicate retrieval of card information without modification or execution. The verb 'get' and 'details' confirm read-only data access.
Attacks that exploit this kind of access
Get card profile/details by card account ID. It is categorised as a Read tool in the PEX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PEX MCP Server MCP server in PolicyLayer and add a rule for pex_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 PEX MCP Server. Nothing to install.
pex_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 pex_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 pex_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.
pex_get_card is provided by the PEX MCP Server MCP server (pexcard/mcp). 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 →