templates_list
List available sandbox templates with metadata for catalog UI: tier (chat-embed/coding-harness/autonomous/custom/base), display name, description, required env vars and connection modes. Used by ghosty.studio to render dynamic
This record as markdown: /tools/cloud-easybits-easybits/templates-list.md
What templates_list does on EasyBits
AI agents call templates_list to retrieve information from EasyBits without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why templates_list is rated Low
Tool retrieves template metadata without modification or execution side effects.
From the tool's definition List available sandbox templates with metadata for catalog UI
Attacks that exploit this kind of access
The rule that runs templates_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For templates_list, this is the rule to start with:
templates_list 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 EasyBits, apply this rule, and every templates_list call is checked against it from then on.
Questions about templates_list
List available sandbox templates with metadata for catalog UI: tier (chat-embed/coding-harness/autonomous/custom/base), display name, description, required env vars and connection modes. Used by ghosty.studio to render dynamic. It is categorised as a Read tool in the EasyBits MCP Server, which means it retrieves data without modifying state.
Register the EasyBits MCP server in PolicyLayer and add a rule for templates_list: 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 EasyBits. Nothing to install.
templates_list 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 templates_list 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 templates_list. 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.
templates_list is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue