Get current operating hours and open/closed status for all recreation facilities
AI agents call get_facility_hours 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 retrieves facility status information without modifying, creating, deleting, or executing any operations. It is a simple informational query about recreation facility hours and open/closed status. There is no risk of data modification, code execution, or financial impact. Severity is low because misuse would only expose publicly-available facility information.
From the tool's definition Tool name 'get_facility_hours' and description 'Get current operating hours and open/closed status' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Get current operating hours and open/closed status for all recreation 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_hours: 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_hours 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_hours 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_hours. 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_hours 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 →