Low Risk

logs

Retrieves container logs as structured line arrays.

How to control logs ↓

What logs does on Make

AI agents call logs 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.

Low Risk

Why logs needs a policy

This tool retrieves and returns log data from containers. The verb 'Retrieves' and the absence of any modification, deletion, or execution semantics clearly place this in the Read category. There is no indication the tool can create, modify, delete, or execute operations—it only queries and returns structured log information.

From the tool's definition Tool name 'logs' and description 'Retrieves container logs as structured line arrays' indicate a read-only operation that queries and returns existing log data without modification or side effects.

Documented attack patterns abuse exactly the kind of access logs gives an agent:

How to control logs

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 logs:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "logs": {}
  }
}

logs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Make — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about logs

What does the logs tool do? +

Retrieves container logs as structured line arrays. It is categorised as a Read tool in the Make MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on logs? +

Register the Make MCP server in PolicyLayer and add a rule for logs: 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.

What risk level is logs? +

logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit logs? +

Yes. Add a rate_limit block to the logs 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.

How do I block logs completely? +

Set action: deny in the PolicyLayer policy for logs. 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.

What MCP server provides logs? +

logs 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.

Enforce policy on every Make tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.