AI agents call query_token to retrieve information from Vnpay without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries existing card token data without creating, modifying, or deleting records. It is a Read category tool. Severity is medium rather than low because the queried data involves sensitive payment card tokenization information, which if exposed could be valuable to attackers, but the tool itself does not enable direct financial transactions or data destruction.
From the tool's definition Tool name is 'query_token' and description states 'Query card token information.' The verb 'Query' and action of retrieving token information indicates a read operation with no modification of data.
Attacks that exploit this kind of access
Query card token information. It is categorised as a Read tool in the Vnpay MCP Server, which means it retrieves data without modifying state.
Register the Vnpay MCP server in PolicyLayer and add a rule for query_token: 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 Vnpay. Nothing to install.
query_token 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 query_token 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 query_token. 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.
query_token is provided by the Vnpay MCP server (theyahia/vnpay-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 →