Upload a chat session to Magnet for tracking and analysis. Returns the created chat with a viewUrl to see it in the web UI.
AI agents use upload_chat to create or update resources in Magnet MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Magnet MCP Server environment.
An AI agent can call upload_chat faster than any human can review — one bad instruction and it creates or modifies resources in Magnet MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Upload a chat session to Magnet for tracking and analysis. Returns the created chat with a viewUrl to see it in the web UI. It is categorised as a Write tool in the Magnet MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Magnet MCP Server MCP server in PolicyLayer and add a rule for upload_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 Magnet MCP Server. Nothing to install.
upload_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 upload_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 upload_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.
upload_chat is provided by the Magnet MCP Server MCP server (toolkit-ai/magnet-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.