Suggest a new source for the archive corpus. Team reviews all submissions.
AI agents use colosseum_suggest_source to create or update resources in Colosseum Copilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Colosseum Copilot environment.
This tool submits a suggestion to a human review queue — it creates a new submission/record but does not directly modify the archive corpus. It is reversible (the team can reject it) and has no destructive or financial implications. Write is the most appropriate category since it posts data to an external system.
From the tool's definition 'Suggest a new source for the archive corpus. Team reviews all submissions.'
Attacks that exploit this kind of access
Suggest a new source for the archive corpus. Team reviews all submissions. It is categorised as a Write tool in the Colosseum Copilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Colosseum Copilot MCP server in PolicyLayer and add a rule for colosseum_suggest_source: 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 Colosseum Copilot. Nothing to install.
colosseum_suggest_source 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 colosseum_suggest_source 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 colosseum_suggest_source. 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.
colosseum_suggest_source is provided by the Colosseum Copilot MCP server (securecheckio/colosseum-copilot-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 →