get-document-blueprint-by-id-array
Gets document blueprints by IDs (or empty array if no IDs are provided)
This record as markdown: /tools/mcp-dev/get-document-blueprint-by-id-array.md
What get-document-blueprint-by-id-array does on Mcp Dev
AI agents call get-document-blueprint-by-id-array 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-document-blueprint-by-id-array is rated Low
This tool retrieves document blueprint data from Umbraco CMS based on provided IDs. It has no side effects - it does not create, modify, delete, or execute operations. The worst-case misuse would be unauthorized information disclosure of blueprint configurations, which is a lower-severity risk compared to write/destructive/execute operations.
From the tool's definition Tool description states it 'Gets document blueprints by IDs' - a retrieval operation with no modification capability. The phrase 'Gets' and the reference to querying by IDs indicates a read-only query operation.
Attacks that exploit this kind of access
The rule that runs get-document-blueprint-by-id-array 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-document-blueprint-by-id-array, this is the rule to start with:
get-document-blueprint-by-id-array 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-document-blueprint-by-id-array call is checked against it from then on.
Questions about get-document-blueprint-by-id-array
Gets document blueprints by IDs (or empty array if no IDs are provided). 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-document-blueprint-by-id-array: 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-document-blueprint-by-id-array 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-document-blueprint-by-id-array 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-document-blueprint-by-id-array. 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-document-blueprint-by-id-array 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