get_messages
AI agents call get_messages to retrieve information from Smartschool MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves messages from an educational account, consistent with 'Read' category operations like fetch and query. The empty description lowers confidence slightly, but the 'get_' naming convention and context of similar read-only sibling tools (get_courses, get_schedule, get_results) strongly indicate data retrieval with no side effects. Educational message access poses low risk if misused by an AI agent.
From the tool's definition Tool name 'get_messages' and server description indicate retrieval of messages from a Smartschool account. No indication of modification, deletion, or execution. Sibling tools are all 'get_*' operations suggesting read-only access pattern.
Attacks that exploit this kind of access
get_messages. It is categorised as a Read tool in the Smartschool MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Smartschool MCP Server MCP server in PolicyLayer and add a rule for get_messages: 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 Smartschool MCP Server. Nothing to install.
get_messages 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_messages 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_messages. 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_messages is provided by the Smartschool MCP Server MCP server (maurodruwel/smartschool-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 →