AI agents use create_prompt 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.
This tool creates new prompts for monitoring purposes. Creation of data entities is a Write operation. The severity is low because prompts are metadata used for analytics—creating them has no direct impact on sensitive data, financial systems, or system integrity. The operation is reversible (can be deleted via delete_prompt). No code execution, data deletion, or financial implications are present.
From the tool's definition Tool name 'create_prompt' and description 'Create a new search prompt' indicate data creation. The tool creates a new monitored prompt entity with required parameters (prompt text and country code), which is a reversible write operation.
Attacks that exploit this kind of access
Create a new search prompt to monitor across AI models. Requires prompt text and country code. 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 create_prompt: 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.
create_prompt 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 create_prompt 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 create_prompt. 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.
create_prompt 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 →