Search for OSU classes by keyword, subject, instructor, etc.
AI agents call search_classes 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 performs a search/query function to retrieve class information from Ohio State University's academic database. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. It is a straightforward read operation that matches the 'Read' category definition of retrieving or querying data with no side effects.
From the tool's definition Tool name 'search_classes' and description 'Search for OSU classes by keyword, subject, instructor, etc.' indicate a query operation that retrieves class information without modifying, executing, or deleting data.
Attacks that exploit this kind of access
Search for OSU classes by keyword, subject, instructor, etc. 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 search_classes: 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.
search_classes 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 search_classes 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 search_classes. 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.
search_classes 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 →