Resolve a football entity (player, team, or coach) to get cross-provider IDs. Use when you need to map between Transfermarkt, FBref, Sofascore, Opta, and other provider IDs, or when you need to look up a player/team/coach by name.
AI agents call resolve_entity to retrieve information from Football Docs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and maps identifier data across providers for football entities. It is a read-only lookup with no ability to modify, delete, or execute anything. Misuse risk is minimal as it only returns reference data.
From the tool's definition 'Resolve a football entity...to get cross-provider IDs' and 'look up a player/team/coach by name' — purely a lookup/mapping operation with no side effects
Documented attack patterns abuse exactly the kind of access resolve_entity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Football Docs, and nothing reaches the server without passing your rules. This is the rule we recommend for resolve_entity:
{
"version": "1",
"default": "deny",
"tools": {
"resolve_entity": {}
}
}resolve_entity 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.
Resolve a football entity (player, team, or coach) to get cross-provider IDs. Use when you need to map between Transfermarkt, FBref, Sofascore, Opta, and other provider IDs, or when you need to look up a player/team/coach by name. It is categorised as a Read tool in the Football Docs MCP Server, which means it retrieves data without modifying state.
Register the Football Docs MCP server in PolicyLayer and add a rule for resolve_entity: 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 Football Docs. Nothing to install.
resolve_entity 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 resolve_entity 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 resolve_entity. 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.
resolve_entity is provided by the Football Docs MCP server (withqwerty/football-docs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Football Docs, 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.
5 Football Docs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.