get-template-query-settings
Returns schema for template queries: available document types, properties, and operators
This record as markdown: /tools/mcp-dev/get-template-query-settings.md
What get-template-query-settings does on Mcp Dev
AI agents call get-template-query-settings to retrieve information from Mcp Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-template-query-settings is rated Low
This tool retrieves configuration and schema information about template queries in Umbraco CMS. It returns available options (document types, properties, operators) without performing any side effects, data modifications, deletions, or financial transactions. This is a straightforward read operation with minimal risk if an AI agent calls it.
From the tool's definition Tool name 'get-template-query-settings' and description 'Returns schema for template queries: available document types, properties, and operators' indicate a retrieval operation that queries and returns metadata/schema information without modifying any data.
Attacks that exploit this kind of access
The rule that runs get-template-query-settings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-template-query-settings, this is the rule to start with:
get-template-query-settings 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 Dev, apply this rule, and every get-template-query-settings call is checked against it from then on.
Questions about get-template-query-settings
Returns schema for template queries: available document types, properties, and operators. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for get-template-query-settings: 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 Dev. Nothing to install.
get-template-query-settings 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-query-settings 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-query-settings. 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-query-settings is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
This server
Across the catalogue