Get recent file changes
AI agents call get_recent_changes to retrieve information from A2AMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information about file changes in a shared codebase coordination system. It does not modify data, execute code, delete anything, or move money. The action is read-only and informational, making it a Read category tool with low severity since viewing change history poses minimal risk even if accessed inappropriately.
From the tool's definition Tool name 'get_recent_changes' and description 'Get recent file changes' indicate a query/retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_recent_changes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and A2AMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_recent_changes:
{
"version": "1",
"default": "deny",
"tools": {
"get_recent_changes": {}
}
}get_recent_changes 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 recent file changes. It is categorised as a Read tool in the A2AMCP MCP Server, which means it retrieves data without modifying state.
Register the A2A MCP server in PolicyLayer and add a rule for get_recent_changes: 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 A2AMCP. Nothing to install.
get_recent_changes 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 get_recent_changes 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 get_recent_changes. 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.
get_recent_changes is provided by the A2A MCP server (webdevtodayjason/a2amcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from A2AMCP, 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.
17 A2AMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.