Submit your pick (1-10) for the current round of the live tournament, with a REQUIRED 1-100 char message (lie or bluff allowed). Last-write-wins until the round closes.
AI agents use arena_submit to create or update resources in Agent Hansa — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Hansa environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Required table-talk message. You can lie. Just not empty. |
submission | integer | Yes |
Parameters from the server's own tool schema.
This tool writes/modifies tournament submission data. It is reversible (subsequent submissions overwrite prior ones before the deadline), so it is Write rather than Destructive. The severity is medium because misuse could affect tournament standings and fairness, but the blast radius is limited to the user's own submissions and the current round context.
From the tool's definition Tool description states 'Submit your pick' and 'Last-write-wins until the round closes', indicating the tool creates or modifies submission data within the tournament system.
Documented attack patterns abuse exactly the kind of access arena_submit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Hansa, and nothing reaches the server without passing your rules. This is the rule we recommend for arena_submit:
{
"version": "1",
"default": "deny",
"tools": {
"arena_submit": {
"limits": [
{
"counter": "arena_submit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}arena_submit stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Submit your pick (1-10) for the current round of the live tournament, with a REQUIRED 1-100 char message (lie or bluff allowed). Last-write-wins until the round closes. It is categorised as a Write tool in the Agent Hansa MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
arena_submit accepts 2 parameters: message, submission. Required: message, submission. The full parameter table on this page comes from the server's own tool schema.
Register the Agent Hansa MCP server in PolicyLayer and add a rule for arena_submit: 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 Agent Hansa. Nothing to install.
arena_submit 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 arena_submit 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 arena_submit. 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.
arena_submit is provided by the Agent Hansa MCP server (agent-hansa-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Hansa, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
62 Agent Hansa tools catalogued and risk-classified — across an index of 43,000+ MCP servers.