Build a preview bundle and return the URL
AI agents invoke get_preview_url to trigger actions in Prowpt MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
While the tool returns a URL (read-like), it first triggers a build process (bundle compilation), which constitutes executing an external operation. The blast radius is medium since a misused build could consume resources or produce unintended artifacts, but it does not modify persistent data directly.
From the tool's definition 'Build a preview bundle and return the URL' — the tool actively builds/compiles a bundle, which is an execution operation, not merely a read
Attacks that exploit this kind of access
Build a preview bundle and return the URL. It is categorised as a Execute tool in the Prowpt MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Prowpt MCP Server MCP server in PolicyLayer and add a rule for get_preview_url: 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 Prowpt MCP Server. Nothing to install.
get_preview_url is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the get_preview_url 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_preview_url. 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_preview_url is provided by the Prowpt MCP Server MCP server (prowptai/prowpt-mcp-server). 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 →