add_content_source
AI agents use add_content_source to create or update resources in Learning Coach MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Learning Coach MCP Server environment.
The tool creates or registers a new content source in the system. This modifies the system's state by expanding available data inputs. While reversible (sources can be removed), it is not a destructive operation. It does not execute arbitrary code or cause financial impact. Write is the appropriate category for this configuration/data creation action.
From the tool's definition Tool name 'add_content_source' indicates creating/adding a new data entry. Server context shows content sources (blogs, RSS feeds, Reddit) are managed as part of the learning system.
Attacks that exploit this kind of access
add_content_source. It is categorised as a Write tool in the Learning Coach MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Learning Coach MCP Server MCP server in PolicyLayer and add a rule for add_content_source: 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 Learning Coach MCP Server. Nothing to install.
add_content_source 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_content_source 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_content_source. 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_content_source is provided by the Learning Coach MCP Server MCP server (pevansh/learning_coach_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 →