Get information about a specific WordPress code changeset/commit including commit message, author, and diff.
AI agents call getChangeset to retrieve information from WordPress Trac MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
getChangeset queries existing version control and commit history data without side effects. It falls clearly under the Read category. The severity is low because retrieving publicly available commit information poses minimal risk; an AI agent cannot cause harm by reading changeset data. Confidence is high given the explicit retrieval-only nature of the description.
From the tool's definition Tool retrieves information about a specific WordPress code changeset/commit, fetching commit message, author, and diff data from Trac. No modification, deletion, or code execution occurs—it is purely a data retrieval operation.
Documented attack patterns abuse exactly the kind of access getChangeset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress Trac MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getChangeset:
{
"version": "1",
"default": "deny",
"tools": {
"getChangeset": {}
}
}getChangeset is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get information about a specific WordPress code changeset/commit including commit message, author, and diff. It is categorised as a Read tool in the WordPress Trac MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress Trac MCP Server MCP server in PolicyLayer and add a rule for getChangeset: 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 WordPress Trac MCP Server. Nothing to install.
getChangeset is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getChangeset 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 getChangeset. 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.
getChangeset is provided by the WordPress Trac MCP Server MCP server (jameswlepage/trac-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WordPress Trac MCP Server, 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.
7 WordPress Trac MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.