Get the current arena tournament accepting joins.
AI agents call arena_upcoming 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 is a retrieval operation that queries tournament information. It has no side effects—it does not create, modify, delete, or execute any actions. The verb 'Get' and the read-only nature of fetching tournament data clearly places this in the Read category. Severity is low as misuse poses minimal risk (an agent would simply retrieve information about an arena tournament).
From the tool's definition Tool name 'arena_upcoming' and description 'Get the current arena tournament accepting joins' indicate a query operation that retrieves information about an upcoming tournament without modifying any state.
Documented attack patterns abuse exactly the kind of access arena_upcoming 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_upcoming:
{
"version": "1",
"default": "deny",
"tools": {
"arena_upcoming": {}
}
}arena_upcoming 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 current arena tournament accepting joins. 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_upcoming: 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_upcoming 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_upcoming 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_upcoming. 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_upcoming 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.