Manage bet visibility for the /fantasy table. action=
AI agents use manage_hidden_bets 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.
This tool modifies the visibility/metadata of existing bets rather than creating new ones or deleting them, classifying it as Write. Severity is medium because misuse could mislead other users about bet visibility or expose/hide bets inappropriately, but it does not irreversibly destroy data (Destructive) or move money (Financial).
From the tool's definition Tool name 'manage_hidden_bets' and description 'Manage bet visibility' indicate modification of bet visibility state in a fantasy betting table. The incomplete description ('action=') suggests parameter-driven write operations to alter bet metadata.
Attacks that exploit this kind of access
Manage bet visibility for the /fantasy table. action=. 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.
Register the PropProfessor MCP server in PolicyLayer and add a rule for manage_hidden_bets: 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.
manage_hidden_bets is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_hidden_bets 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 manage_hidden_bets. 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.
manage_hidden_bets 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 →