Create a new conversation for an agent.
AI agents use create_conversation to create or update resources in CustomGPT MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CustomGPT MCP Server environment.
Creating a conversation is a write operation that generates new data but is fully reversible (conversations can be deleted via the sibling 'delete_conversation' tool). It has minimal blast radius – worst case, it creates unused conversation records that can be cleaned up. No code execution, data deletion, or financial impact.
From the tool's definition Tool name is 'create_conversation' and description states it 'Create a new conversation for an agent' – a reversible data creation action with no destructive or execute-like side effects.
Attacks that exploit this kind of access
Create a new conversation for an agent. It is categorised as a Write tool in the CustomGPT MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CustomGPT MCP Server MCP server in PolicyLayer and add a rule for create_conversation: 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 CustomGPT MCP Server. Nothing to install.
create_conversation 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_conversation 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_conversation. 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_conversation is provided by the CustomGPT MCP Server MCP server (poll-the-people/customgpt-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 →