View current status of all submitted applications
AI agents call view_application_status to retrieve information from LMS 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 and displays existing application status information. It has no side effects—it does not create, modify, delete, or execute operations. The action is purely read-based, querying academic data (application statuses) similar to other sibling read tools like check_attendance, get_marks, and get_timetable.
From the tool's definition Tool name 'view_application_status' and description 'View current status of all submitted applications' indicate retrieval of application status data with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
View current status of all submitted applications. It is categorised as a Read tool in the LMS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LMS MCP Server MCP server in PolicyLayer and add a rule for view_application_status: 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 LMS MCP Server. Nothing to install.
view_application_status 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 view_application_status 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 view_application_status. 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.
view_application_status is provided by the LMS MCP Server MCP server (qaziabsaar/lms_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 →