log_pick · PropProfessor MCP: Risk & Policy

WHAT IT DOES

What log_pick does on PropProfessor MCP

AI agents use log_pick to create or update resources in PropProfessor MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PropProfessor MCP environment.

WHY IT NEEDS A POLICY

Why log_pick needs a policy

This tool writes/creates a new record of a placed bet into a personal tracking system. It does not move money or place a live wager — it only logs historical bet data — so it's Write rather than Financial. Misuse could result in corrupted or misleading betting records, hence medium severity.

From the tool's definition 'Log a bet you placed', 'Records game, league, market, selection, odds, stake', 'track your personal betting performance'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_pick Rate-limited

log_pick stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "log_pick": {
      "limits": [
        {
          "counter": "log_pick_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PropProfessor MCP, so you can run agents against it safely.

FAQ

Questions about log_pick

What does the log_pick tool do? +

Log a bet you placed before tip-off. Records game, league, market, selection, odds, stake, and optional metadata. Use this to track your personal betting performance and compare against the system recommendations. It is categorised as a Write tool in the PropProfessor MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_pick? +

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

log_pick is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit log_pick? +

Yes. Add a rate_limit block to the log_pick 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 log_pick completely? +

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

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