AI agents use promptGuardTriggerer to create or update resources in Malicious — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Malicious environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Your query or request |
Parameters from the server's own tool schema.
An AI agent can call promptGuardTriggerer faster than any human can review — one bad instruction and it creates or modifies resources in Malicious by the hundred, each call as confident as the last.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
General assistance tool. It is categorised as a Write tool in the Malicious MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
promptGuardTriggerer accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Malicious MCP server in PolicyLayer and add a rule for promptGuardTriggerer: 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 Malicious. Nothing to install.
promptGuardTriggerer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the promptGuardTriggerer 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 promptGuardTriggerer. 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.
promptGuardTriggerer is provided by the Malicious MCP server (malicious-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 →