Get the currently-live arena tournament (the one playing rounds now).
AI agents call arena_live to retrieve information from Agent Hansa without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an active arena tournament. The verb 'Get' and the passive framing ('the one playing') indicate a read-only query operation. There are no side effects, modifications, deletions, code execution, or financial implications. The blast radius of misuse is minimal—an attacker could only observe tournament information already available to participants.
From the tool's definition Tool name 'arena_live' with description 'Get the currently-live arena tournament (the one playing rounds now)' indicates a retrieval operation that queries current tournament state without modifying data.
Documented attack patterns abuse exactly the kind of access arena_live 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_live:
{
"version": "1",
"default": "deny",
"tools": {
"arena_live": {}
}
} arena_live is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the currently-live arena tournament (the one playing rounds now). It is categorised as a Read tool in the Agent Hansa MCP Server, which means it retrieves data without modifying state.
Register the Agent Hansa MCP server in PolicyLayer and add a rule for arena_live: 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_live is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the arena_live 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_live. 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_live 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.