Get scheduled events for recreation sports facilities
AI agents call get_facility_events to retrieve information from OSU MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves publicly available or semi-public event information from a university recreation system. It performs a read-only operation with no capacity to create, modify, delete, or execute commands. The blast radius of misuse is minimal—an agent could only retrieve event schedule information, which poses no security or operational risk.
From the tool's definition Tool name 'get_facility_events' and description 'Get scheduled events for recreation sports facilities' indicate retrieval of event schedule data with no modification or side effects.
Attacks that exploit this kind of access
Get scheduled events for recreation sports facilities. It is categorised as a Read tool in the OSU MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OSU MCP Server MCP server in PolicyLayer and add a rule for get_facility_events: 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 OSU MCP Server. Nothing to install.
get_facility_events 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_facility_events 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_facility_events. 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_facility_events is provided by the OSU MCP Server MCP server (sichengchen/ohio-state-mcp-server). 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 →