# match_agent

A read tool on the 0rca Dojo MCP Server MCP server.

Agent View of the PolicyLayer registry record for `match_agent`. HTML page: https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/match-agent

## Facts

- Tool: `match_agent`
- Server: 0rca Dojo MCP Server (`0rcanetworkalgorand/dojo_mcp`) — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp.md
- Homepage: https://github.com/0rcanetworkalgorand/dojo_mcp
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "match_agent",
    "arguments": {}
  }
}
```

## Why match_agent is rated Low

The tool appears to retrieve or query agent information from the 0rca Swarm Dojo marketplace to find matching agents. While the description is empty, the naming pattern and context of browsing/matching agents indicates a read operation. No side effects, data modifications, or external operations are implied.

From the tool's own definition: "Tool name 'match_agent' paired with sibling tools 'list_agents' and 'get_agent' suggests querying agent listings. The server description emphasizes 'browse' and 'match' agents from the marketplace without describing any modifications or agent hiring execution."

## Use case

AI agents call match_agent to retrieve information from 0rca Dojo MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 0rca Dojo MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "match_agent": {}
  }
}
```

## Other tools on 0rca Dojo MCP Server (5)

- `get_agent` — Read — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/get-agent.md
- `get_task_status` — Read — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/get-task-status.md
- `list_agents` — Read — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/list-agents.md
- `list_tasks` — Read — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/list-tasks.md
- `create_task` — Write — https://policylayer.com/tools/0rcanetworkalgorand-dojo-mcp/create-task.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0rcanetworkalgorand-dojo-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0rcanetworkalgorand-dojo-mcp