Get the academic calendar with important dates
AI agents call get_academic_calendar 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 static calendar information (dates of academic events/deadlines) from OSU's system. It performs a query operation that returns data without creating, modifying, deleting, or executing anything. The low severity reflects minimal risk—even if an AI agent retrieves this data, the harm is negligible since it's informational, non-sensitive, and publicly available institutional calendar data.
From the tool's definition Tool name 'get_academic_calendar' and description 'Get the academic calendar with important dates' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the academic calendar with important dates. 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_academic_calendar: 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_academic_calendar 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_academic_calendar 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_academic_calendar. 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_academic_calendar 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 →