Generate HTML and React embed code for displaying a secure prompt badge.
AI agents call get_embed_code to retrieve information from HashBuilds Secure Prompts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-like operation that retrieves and formats embed code for a badge display. It does not execute arbitrary code, modify core data structures, delete anything, or trigger external operations. The output is static embed code intended for embedding on websites. While it produces code, it does not execute it or perform side effects.
From the tool's definition Tool generates HTML and React embed code for displaying a badge. The description indicates it creates output content (code snippets) for display purposes without modifying backend systems or data.
Attacks that exploit this kind of access
Generate HTML and React embed code for displaying a secure prompt badge. It is categorised as a Read tool in the HashBuilds Secure Prompts MCP Server, which means it retrieves data without modifying state.
Register the HashBuilds Secure Prompts MCP server in PolicyLayer and add a rule for get_embed_code: 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 HashBuilds Secure Prompts. Nothing to install.
get_embed_code 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_embed_code 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_embed_code. 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_embed_code is provided by the HashBuilds Secure Prompts MCP server (jphyqr/secure-prompts-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 →