Returns available evaluation tools, what they check, and their pricing. Call this first to understand what Axcess can evaluate and how much each evaluation costs. This tool is FREE. All evaluation tools require USDC payment on Base network. Returns: JSON with tool descriptions, pricing, and rubri...
AI agents call list_capabilities to retrieve information from Axcess 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 metadata about the MCP server's capabilities and pricing—a read-only information retrieval operation. It has no side effects on data, no execution of evaluations, no financial transactions, and no destructive operations. It serves purely to inform the user about available services.
From the tool's definition Tool name is 'list_capabilities' and description states 'Returns available evaluation tools, what they check, and their pricing.' This retrieves information about available tools without creating, modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Returns available evaluation tools, what they check, and their pricing. Call this first to understand what Axcess can evaluate and how much each evaluation costs. This tool is FREE. All evaluation tools require USDC payment on Base network. Returns: JSON with tool descriptions, pricing, and rubric categories. It is categorised as a Read tool in the Axcess MCP Server, which means it retrieves data without modifying state.
Register the Axcess MCP server in PolicyLayer and add a rule for list_capabilities: 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 Axcess. Nothing to install.
list_capabilities 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_capabilities 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_capabilities. 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_capabilities is provided by the Axcess MCP server (sicxz/axcess-mcp-server). 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 →