Create a new AI chat session in Sure.
AI agents use create_chat to create or update resources in Sure MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sure MCP Server environment.
The tool creates a new chat session, which is a write operation that generates new data in the system. It is reversible (sessions can be deleted as evidenced by the sibling delete_chat tool) and has no destructive, financial, or code execution properties. Low severity because creating a chat session poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'create_chat' and description 'Create a new AI chat session' indicate creation of a new record/session without permanent deletion or financial impact. This is a write operation that creates reversible data.
Attacks that exploit this kind of access
Create a new AI chat session in Sure. It is categorised as a Write tool in the Sure MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sure MCP Server MCP server in PolicyLayer and add a rule for create_chat: 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 Sure MCP Server. Nothing to install.
create_chat 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_chat 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_chat. 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_chat is provided by the Sure MCP Server MCP server (robcerda/sure-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 →