get_pick_stats

Get your personal betting performance stats: win rate, profit/loss, breakdowns by league and confidence tier. Helps you see what strategies are working. Call for a SESSION OR WEEKLY RECAP — pass

Server PropProfessor MCP j17drake/propprofessor-mcp
Category Read
Risk class Low
Parameters 00 required

What get_pick_stats does on PropProfessor MCP

AI agents call get_pick_stats 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.

Why get_pick_stats needs a policy

This tool retrieves and aggregates user's past betting statistics and performance metrics. It has no side effects, does not modify data, execute code, delete records, or move money. It is purely informational/analytical in nature, making it a Read category risk with low severity since misuse would only expose personal performance data rather than enable harmful actions.

From the tool's definition Tool description states 'Get your personal betting performance stats' and 'Helps you see what strategies are working.' This is a retrieval operation that queries historical betting data and returns analytics/summaries without modifying any data.

Questions about get_pick_stats

What does the get_pick_stats tool do? +

Get your personal betting performance stats: win rate, profit/loss, breakdowns by league and confidence tier. Helps you see what strategies are working. Call for a SESSION OR WEEKLY RECAP — pass. It is categorised as a Read tool in the PropProfessor MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_pick_stats? +

Register the PropProfessor MCP server in PolicyLayer and add a rule for get_pick_stats: 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.

What risk level is get_pick_stats? +

get_pick_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_pick_stats? +

Yes. Add a rate_limit block to the get_pick_stats 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.

How do I block get_pick_stats completely? +

Set action: deny in the PolicyLayer policy for get_pick_stats. 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.

What MCP server provides get_pick_stats? +

get_pick_stats 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.