Get the full field schema for a specific DocRenders template, including field types, descriptions, and examples.
AI agents call get_template to retrieve information from Docrenders without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves template schema metadata (field types, descriptions, examples) for informational purposes only. It has no side effects, cannot modify or delete data, and poses minimal risk even if misused by an AI agent. The worst-case scenario is retrieving schema information that is not sensitive.
From the tool's definition Tool description states it 'Get[s] the full field schema for a specific DocRenders template' — a retrieval operation with no data creation, modification, or deletion.
Attacks that exploit this kind of access
Get the full field schema for a specific DocRenders template, including field types, descriptions, and examples. It is categorised as a Read tool in the Docrenders MCP Server, which means it retrieves data without modifying state.
Register the Docrenders MCP server in PolicyLayer and add a rule for 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 Docrenders. Nothing to install.
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 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 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.
get_template is provided by the Docrenders MCP server (jwhist/docrenders-mcp). 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 →