Project what the student\
AI agents call simulate_grade_scenario to retrieve information from School MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Simulating grade scenarios is a read-only analytical operation. It queries live school data to model hypothetical outcomes without creating, modifying, deleting, or executing external actions. The tool generates projections and forecasts to help students understand potential grade changes, but does not alter actual grades, records, or systems.
From the tool's definition Tool name 'simulate_grade_scenario' and context indicates it 'Project[s] what the student' (description cuts off, but implies forecasting/modeling). The sibling tools are all Read operations (get_*, ask_about_*, calculate_*).
Attacks that exploit this kind of access
Project what the student\. It is categorised as a Read tool in the School MCP MCP Server, which means it retrieves data without modifying state.
Register the School MCP server in PolicyLayer and add a rule for simulate_grade_scenario: 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 School MCP. Nothing to install.
simulate_grade_scenario 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 simulate_grade_scenario 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 simulate_grade_scenario. 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.
simulate_grade_scenario is provided by the School MCP server (shengdynasty/school-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 →