get_instructor_schedules
AI agents call get_instructor_schedules to retrieve information from Scottylabs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves instructor schedule information from the CMU course catalog without side effects, side effects, or data modification. The 'get_' prefix and context within a read-focused server confirm it is a simple data retrieval operation with minimal risk if misused.
From the tool's definition Tool name 'get_instructor_schedules' indicates retrieval of schedule data. Server description states it 'retrieves course details, schedules, prerequisites, and instructor information' with no mention of modification or execution capabilities.
Attacks that exploit this kind of access
get_instructor_schedules. It is categorised as a Read tool in the Scottylabs MCP Server, which means it retrieves data without modifying state.
Register the Scottylabs MCP server in PolicyLayer and add a rule for get_instructor_schedules: 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 Scottylabs. Nothing to install.
get_instructor_schedules 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_instructor_schedules 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_instructor_schedules. 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_instructor_schedules is provided by the Scottylabs MCP server (shivendoo123/scottylabs_mcp). 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 →