Get full details (including line history, consensus, movement debug) for specific plays by game ID. Generic market names are auto-resolved per league. Each row includes
AI agents call get_play_details to retrieve information from PropProfessor MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical and analytical data about plays/games without creating, modifying, or deleting any information. It is purely informational and poses minimal security risk if misused by an AI agent.
From the tool's definition Tool name 'get_play_details' and description explicitly states it retrieves 'full details' for plays—a query operation that 'includes line history, consensus, movement debug.' The verb 'Get' and the retrieval-only nature indicate no modification or side…
Attacks that exploit this kind of access
Get full details (including line history, consensus, movement debug) for specific plays by game ID. Generic market names are auto-resolved per league. Each row includes. It is categorised as a Read tool in the PropProfessor MCP MCP Server, which means it retrieves data without modifying state.
Register the PropProfessor MCP server in PolicyLayer and add a rule for get_play_details: 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 PropProfessor MCP. Nothing to install.
get_play_details 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 get_play_details 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 get_play_details. 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.
get_play_details is provided by the PropProfessor MCP server (j17drake/propprofessor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →