AI agents use add_lesson to create or update resources in LinguaMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LinguaMCP environment.
This tool creates new lesson content within the structured curriculum, constituting a Write operation. It reversibly adds data (lessons can presumably be removed via the sibling tool 'remove_lesson'). The severity is low because adding educational content has minimal blast radius—worst case, unwanted lessons are created but can be deleted. No destructive, financial, or code execution capability is involved.
From the tool's definition Tool description states 'Add a new lesson to a chapter', which is a create operation that modifies the curriculum data by inserting a new lesson resource.
Attacks that exploit this kind of access
Add a new lesson to a chapter. Returns the new lesson ID. It is categorised as a Write tool in the LinguaMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lingua MCP server in PolicyLayer and add a rule for add_lesson: 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 LinguaMCP. Nothing to install.
add_lesson 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 add_lesson 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 add_lesson. 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.
add_lesson is provided by the Lingua MCP server (marsmanleo/linguamcp). 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 →