Lists all available tools with their names, descriptions, and total count.
AI agents call list_tools to retrieve information from Storyblok MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query/listing operation with no side effects. It retrieves metadata about tools but does not create, modify, delete, execute external operations, or move money. This is a classic Read category tool with minimal security risk.
From the tool's definition Tool name 'list_tools' and description 'Lists all available tools with their names, descriptions, and total count' indicate a read-only operation that retrieves and displays information about available tools without modifying any data.
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 Storyblok MCP Server, 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 all available tools with their names, descriptions, and total count. It is categorised as a Read tool in the Storyblok MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Storyblok MCP Server 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 Storyblok MCP Server. 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 Storyblok MCP Server MCP server (kiran1689/storyblok-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Storyblok MCP Server, 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.
159 Storyblok MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.