Reject a brand suggestion, removing it from the project and preventing it from being re-suggested.
AI agents call reject_brand_suggestion to permanently remove resources in Peecai — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a brand suggestion and blacklists it from being re-suggested, making the action irreversible. This fits the Destructive category since the data cannot be recovered and the suppression of future suggestions is a permanent side effect.
From the tool's definition 'removing it from the project and preventing it from being re-suggested' — the rejection is irreversible and permanently suppresses future re-suggestion
Attacks that exploit this kind of access
Reject a brand suggestion, removing it from the project and preventing it from being re-suggested. It is categorised as a Destructive tool in the Peecai MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Peecai MCP server in PolicyLayer and add a rule for reject_brand_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_brand_suggestion is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reject_brand_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_brand_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_brand_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 →