Get school schedule for a specific date (backward compatibility)
AI agents call get_schedule to retrieve information from N Lobby 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 schedule information without modifying, deleting, or executing operations. It is a straightforward data query operation. The severity is low because school schedule data is not sensitive, and unauthorized access would have minimal impact on the institution or students. The (backward compatibility) note suggests this is a stable, well-understood interface.
From the tool's definition Tool name 'get_schedule' and description 'Get school schedule for a specific date' indicate a retrieval operation with no side effects. The prefix 'get_' and verb 'Get' are characteristic of Read operations.
Documented attack patterns abuse exactly the kind of access get_schedule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and N Lobby MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_schedule:
{
"version": "1",
"default": "deny",
"tools": {
"get_schedule": {}
}
}get_schedule is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get school schedule for a specific date (backward compatibility). It is categorised as a Read tool in the N Lobby MCP Server MCP Server, which means it retrieves data without modifying state.
Register the N Lobby MCP Server MCP server in PolicyLayer and add a rule for get_schedule: 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 N Lobby MCP Server. Nothing to install.
get_schedule 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_schedule 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_schedule. 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_schedule is provided by the N Lobby MCP Server MCP server (minagishl/nlobby-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from N Lobby MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 N Lobby MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.