AI agents call list_tools to retrieve information from AgentPay 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 information about available tools, pricing, and metadata. It performs no modifications, deletions, executions, or financial transactions. The 'No authentication required' note indicates it is informational only. While the server context involves payments, this specific tool only reads/lists data, making it a Read category risk with low severity.
From the tool's definition Tool name is 'list_tools' and description states it 'List[s] all available tools in the AgentPay gateway with their descriptions, methods, and pricing.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all available tools in the AgentPay gateway with their descriptions, methods, and pricing. No authentication required. It is categorised as a Read tool in the AgentPay MCP Server, which means it retrieves data without modifying state.
Register the AgentPay MCP server in PolicyLayer and add a rule for list_tools: 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 AgentPay. Nothing to install.
list_tools 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 list_tools 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 list_tools. 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.
list_tools is provided by the AgentPay MCP server (joepangallo/mcp-server-agentpay). 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 →