list_available_tools
AI agents call list_available_tools to retrieve information from Ultimate-MCP-Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool lists or retrieves information about available tools—a read-only operation with no side effects, data modification, or destructive capability. Low severity reflects minimal risk even if misused by an agent, as it only exposes metadata about the system. Confidence is moderate (0.85) rather than high due to the empty description; however, the name strongly suggests a benign informational operation.
From the tool's definition Tool name 'list_available_tools' indicates a query/enumeration operation that retrieves available tools without modifying data. The empty description provides no contradictory evidence of side effects.
Attacks that exploit this kind of access
list_available_tools. It is categorised as a Read tool in the Ultimate-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the Ultimate-MCP-Server MCP server in PolicyLayer and add a rule for list_available_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 Ultimate-MCP-Server. Nothing to install.
list_available_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_available_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_available_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_available_tools is provided by the Ultimate-MCP-Server MCP server (logos-parthenos-ai/ultimate_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 →