Get full details of a template including its property schema, actions, and factory config.
AI agents call dual_get_template to retrieve information from DUAL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries and returns template configuration data. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an attacker could only gain visibility into template schemas and configuration.
From the tool's definition Tool name contains 'get' and description states 'Get full details of a template' — a retrieval operation with no side effects. Returns template metadata (property schema, actions, factory config) without modifying or executing anything.
Attacks that exploit this kind of access
Get full details of a template including its property schema, actions, and factory config. It is categorised as a Read tool in the DUAL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DUAL MCP Server MCP server in PolicyLayer and add a rule for dual_get_template: 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 DUAL MCP Server. Nothing to install.
dual_get_template 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 dual_get_template 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 dual_get_template. 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.
dual_get_template is provided by the DUAL MCP Server MCP server (ro-ro-b/dual-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 →