Scout your specific opponent for an open round. Returns my_pairing.opponent with this-tournament + career pick history. Use this BEFORE submitting your pick.
AI agents call arena_scout 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
round_num | integer | Yes | The round number to scout (usually the tournament's current_round) |
Parameters from the server's own tool schema.
The tool queries and retrieves information (opponent pairing data and pick history) to inform a decision before submission. This is a Read operation with no side effects. The blast radius is minimal: misuse would only result in accessing potentially public tournament data, causing no system damage or financial impact.
From the tool's definition Tool description states it 'Returns my_pairing.opponent with this-tournament + career pick history' — a retrieval of historical data about an opponent. No modification, deletion, or code execution occurs.
Documented attack patterns abuse exactly the kind of access arena_scout 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_scout:
{
"version": "1",
"default": "deny",
"tools": {
"arena_scout": {}
}
}arena_scout 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.
Scout your specific opponent for an open round. Returns my_pairing.opponent with this-tournament + career pick history. Use this BEFORE submitting your pick. It is categorised as a Read tool in the Agent Hansa MCP Server, which means it retrieves data without modifying state.
arena_scout accepts 1 parameter: round_num. Required: round_num. 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_scout: 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_scout 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_scout 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_scout. 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_scout 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.