render_list_presets
List all available render presets.
This record as markdown: /tools/mcp-anything/render-list-presets.md
What render_list_presets does on Mcp Anything
AI agents call render_list_presets to retrieve information from Mcp Anything without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why render_list_presets is rated Low
This tool retrieves and lists existing render preset configurations. It performs no modifications, deletions, or executions—purely informational. The 'list' verb and passive 'List all available' description confirm it is a Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'render_list_presets' and description 'List all available render presets' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs render_list_presets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For render_list_presets, this is the rule to start with:
render_list_presets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every render_list_presets call is checked against it from then on.
Questions about render_list_presets
List all available render presets. It is categorised as a Read tool in the Mcp Anything MCP Server, which means it retrieves data without modifying state.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for render_list_presets: 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 Mcp Anything. Nothing to install.
render_list_presets 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 render_list_presets 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 render_list_presets. 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.
render_list_presets is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
This server
Across the catalogue