AI agents use reply_to_comment to create or update resources in Edstem — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Edstem environment.
This tool creates new comment data in the Ed Discussion system, modifying the discussion state by adding a reply. This is reversible (replies can be edited or deleted by moderators), so it falls under Write rather than Destructive. Severity is medium because a misused tool could spam or disrupt discussions, but the impact is limited to a single discussion thread and the content can be moderated/removed.
From the tool's definition Tool name 'reply_to_comment' and description 'Reply to an existing comment' indicate content creation. The server description confirms it 'enabling users to manage threads, comments' with 'posting content' capability.
Attacks that exploit this kind of access
Reply to an existing comment. It is categorised as a Write tool in the Edstem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Edstem MCP server in PolicyLayer and add a rule for reply_to_comment: 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 Edstem. Nothing to install.
reply_to_comment 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 reply_to_comment 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 reply_to_comment. 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.
reply_to_comment is provided by the Edstem MCP server (rob-9/edstem-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 →