Get asset errors for a specific checkpoint, with content highlighting the issues
AI agents call get_asset_errors 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 retrieves error information about assets within a checkpoint. It has no side effects—it only queries and returns data about existing issues. The action is observational and read-only, similar to the sibling tool 'get_asset_issues'. Even in a misuse scenario, the worst outcome would be information disclosure, not data loss or operational damage.
From the tool's definition Tool name 'get_asset_errors' and description 'Get asset errors for a specific checkpoint' indicates data retrieval.
Attacks that exploit this kind of access
Get asset errors for a specific checkpoint, with content highlighting the issues. 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 get_asset_errors: 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.
get_asset_errors 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_asset_errors 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_asset_errors. 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_asset_errors 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 →