AI agents use add_resource 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 or modifies lesson metadata by adding a reference to an external resource. It is a Write operation because it creates new data in the system without destructive, financial, or code-execution implications. Severity is low because adding a resource link has minimal blast radius—the worst case is spam or irrelevant resources cluttering the curriculum, which can be removed.
From the tool's definition Tool name 'add_resource' and description 'Add an external resource' indicate creation of new data (a resource link). The action is reversible via the sibling tool 'remove_lesson' or implied delete capability.
Attacks that exploit this kind of access
Add an external resource (YouTube, article, podcast) linked to a lesson. 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_resource: 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_resource 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_resource 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_resource. 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_resource 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 →