Lists the tool definitions of all self-written tools available for use. These tools can be used by calling
AI agents call list_tools to retrieve information from Riza without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available tools without modifying, executing, or deleting anything. It is purely informational—enumerating tool definitions. Even though it reveals what tools exist on the server (which could inform an attacker), the act itself is non-destructive data retrieval, placing it firmly in the Read category with low severity.
From the tool's definition Tool name is 'list_tools' and description states 'Lists the tool definitions of all self-written tools available for use.' The verb 'Lists' and the function of retrieving/enumerating tool definitions indicates a read-only query operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_tools gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Riza, and nothing reaches the server without passing your rules. This is the rule we recommend for list_tools:
{
"version": "1",
"default": "deny",
"tools": {
"list_tools": {}
}
}list_tools is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists the tool definitions of all self-written tools available for use. These tools can be used by calling. It is categorised as a Read tool in the Riza MCP Server, which means it retrieves data without modifying state.
Register the Riza 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 Riza. 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 Riza MCP server (riza-io/riza-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Riza, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Riza tools catalogued and risk-classified — across an index of 43,000+ MCP servers.