Get parameter schema and metadata for a template
AI agents call template_get_schema to retrieve information from Engineering MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata and schema information about templates—a read-only operation with no side effects, data modification, code execution, or destructive capability. The low severity reflects minimal risk even if an agent calls it with unexpected arguments, as it merely returns reference data.
From the tool's definition Tool name 'template_get_schema' and description 'Get parameter schema and metadata for a template' indicate a retrieval operation that queries schema information without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access template_get_schema gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Engineering MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for template_get_schema:
{
"version": "1",
"default": "deny",
"tools": {
"template_get_schema": {}
}
} template_get_schema 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.
Get parameter schema and metadata for a template. It is categorised as a Read tool in the Engineering MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Engineering MCP Server MCP server in PolicyLayer and add a rule for template_get_schema: 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 Engineering MCP Server. Nothing to install.
template_get_schema 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 template_get_schema 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 template_get_schema. 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.
template_get_schema is provided by the Engineering MCP Server MCP server (puran-water/dexpi-sfiles-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Engineering 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.
72 Engineering MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.