Get the HTML content for a specific asset
AI agents call get_asset_content 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/queries HTML content from an asset without creating, modifying, deleting, or executing operations. It is a straightforward read operation consistent with other Read-category tools on this server (get_asset, get_asset_status, etc.). Low severity because reading content poses minimal risk unless the content itself contains sensitive data, but the tool itself performs no dangerous actions.
From the tool's definition Tool name is 'get_asset_content' and description states 'Get the HTML content for a specific asset' — pure retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get the HTML content for a specific asset. 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_content: 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_content 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_content 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_content. 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_content 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 →