Create and submit a new application to the university
AI agents use create_application to create or update resources in LMS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LMS MCP Server environment.
This tool creates and submits a new application, which is a reversible write operation. It modifies university records by adding a new application entry but does not permanently delete data (Destructive), move money (Financial), or execute arbitrary code (Execute).
From the tool's definition Tool description states 'Create and submit a new application to the university' — uses imperative verbs 'create' and 'submit' indicating data creation and modification.
Attacks that exploit this kind of access
Create and submit a new application to the university. It is categorised as a Write tool in the LMS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LMS MCP Server MCP server in PolicyLayer and add a rule for create_application: 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.
create_application is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_application 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 create_application. 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.
create_application 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 →