AI agents use reject_prompt_suggestion to create or update resources in Peecai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Peecai environment.
The action is reversible—rejecting a suggestion can be undone by accepting it or creating a new suggestion. It modifies data (updates suggestion status) without permanently destroying it. The blast radius is minimal as it only affects suggestion metadata within an analytics/search system. This is a Write-category operation: creates or modifies data reversibly.
From the tool's definition Tool name is 'reject_prompt_suggestion' and description states it will 'Reject a prompt suggestion.' This modifies the state of a suggestion record (marking it as rejected) reversibly.
Attacks that exploit this kind of access
Reject a prompt suggestion. It is categorised as a Write tool in the Peecai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Peecai MCP server in PolicyLayer and add a rule for reject_prompt_suggestion: 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 Peecai. Nothing to install.
reject_prompt_suggestion 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 reject_prompt_suggestion 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 reject_prompt_suggestion. 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.
reject_prompt_suggestion is provided by the Peecai MCP server (mcp-server-peecai). 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 →