Search for assets (pages that have been scanned)
AI agents call search_assets to retrieve information from Crownpeak DQM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing assets in the CMS without creating, modifying, deleting, or executing actions. It is a standard read operation typical of content management systems. The low severity reflects minimal blast radius — an agent could over-search but cannot cause data loss or financial harm. Confidence is high due to clear search semantics.
From the tool's definition Tool is described as 'Search for assets (pages that have been scanned)' — a search operation that retrieves or queries data without modification. The verb 'search' and context of finding already-scanned pages indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Search for assets (pages that have been scanned). It is categorised as a Read tool in the Crownpeak DQM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Crownpeak DQM MCP Server MCP server in PolicyLayer and add a rule for search_assets: 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 Crownpeak DQM MCP Server. Nothing to install.
search_assets 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 search_assets 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 search_assets. 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.
search_assets is provided by the Crownpeak DQM MCP Server MCP server (ptylr/crownpeak-dqm-node-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 →