Get information about all OSU buildings including addresses, locations, departments, and room details
AI agents call get_buildings 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 is a read-only tool that queries and retrieves static information about university buildings. It has no side effects, does not modify data, and does not trigger external operations. The low severity reflects minimal risk if misused - an agent could only retrieve building information already publicly available at a university.
From the tool's definition Tool description states 'Get information about all OSU buildings' - retrieves building data including addresses, locations, departments, and room details with no modification or destructive capability.
Attacks that exploit this kind of access
Get information about all OSU buildings including addresses, locations, departments, and room details. 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_buildings: 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_buildings 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_buildings 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_buildings. 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_buildings 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 →