AI agents call log to retrieve information from Make without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves commit history data from a version control system (likely Git). It performs a pure read operation that does not modify, delete, or execute any code. The data returned is historical metadata about commits, which is a non-destructive query operation. Severity is low because commit history is typically non-sensitive metadata and exposure causes no immediate system risk.
From the tool's definition Tool name 'log' and description 'Returns commit history as structured data' indicates retrieval of existing version control information with no modifications or side effects.
Documented attack patterns abuse exactly the kind of access log gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for log:
{
"version": "1",
"default": "deny",
"tools": {
"log": {}
}
}log 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.
Returns commit history as structured data. It is categorised as a Read tool in the Make MCP Server, which means it retrieves data without modifying state.
Register the Make MCP server in PolicyLayer and add a rule for log: 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 Make. Nothing to install.
log 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 log 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 log. 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.
log is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, 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.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.