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...
Part of the Axcess — Design Accessibility Evaluation server.
Free to start. No card required.
AI agents call list_capabilities to retrieve information from Axcess — Design Accessibility Evaluation without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though list_capabilities only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"list_capabilities": {}
}
}See the full Axcess — Design Accessibility Evaluation policy for all 3 tools.
These attack patterns abuse exactly the kind of access list_capabilities gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
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 — Design Accessibility Evaluation MCP Server, which means it retrieves data without modifying state.
Register the Axcess — Design Accessibility Evaluation 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 — Design Accessibility Evaluation. 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 — Design Accessibility Evaluation MCP server (https://axcess-mcp-server.fly.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Axcess — Design Accessibility Evaluation tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.