lesson_plan
AI agents use lesson_plan to create or update resources in EduChain MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EduChain MCP Server environment.
The tool generates lesson plans, which is a reversible creation of data (educational content). It does not execute external systems, delete data, move money, or have destructive effects. The user can regenerate, edit, or discard lesson plans without permanent consequences. Severity is low because misuse results only in unwanted educational content generation with no system-level impact.
From the tool's definition Tool name 'lesson_plan' combined with sibling tools 'generate_flashcards' and 'generate_mcqs' and server description stating it 'enabling creation of...comprehensive lesson plans' indicates this tool creates educational content.
Attacks that exploit this kind of access
lesson_plan. It is categorised as a Write tool in the EduChain MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EduChain MCP Server MCP server in PolicyLayer and add a rule for lesson_plan: 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 EduChain MCP Server. Nothing to install.
lesson_plan 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 lesson_plan 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 lesson_plan. 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.
lesson_plan is provided by the EduChain MCP Server MCP server (taksh-pal/educhain_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 →