AI agents use set_changelog to create or update resources in MCP Conductor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Conductor environment.
This tool creates or modifies changelog entries, which is a reversible write operation. It does not execute code, delete data irreversibly, or move money. The severity is medium because a compromised agent could pollute development history with false entries, potentially misleading teams about project state and changes, but the impact is limited to metadata/documentation rather than core application data or…
From the tool's definition Tool description explicitly states 'Add entry to development changelog' — a creation/modification operation that writes data to a changelog record.
Documented attack patterns abuse exactly the kind of access set_changelog gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Conductor, and nothing reaches the server without passing your rules. This is the rule we recommend for set_changelog:
{
"version": "1",
"default": "deny",
"tools": {
"set_changelog": {
"limits": [
{
"counter": "set_changelog_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_changelog stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add entry to development changelog. It is categorised as a Write tool in the MCP Conductor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Conductor MCP server in PolicyLayer and add a rule for set_changelog: 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 MCP Conductor. Nothing to install.
set_changelog 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 set_changelog 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 set_changelog. 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.
set_changelog is provided by the MCP Conductor MCP server (lutherscottgarcia/mcp-conductor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Conductor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 MCP Conductor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.