render.logs · MCP Fullstack MCP: Risk & Policy

WHAT IT DOES

What render.logs does on MCP Fullstack

AI agents call render.logs to retrieve information from MCP Fullstack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

WHY IT NEEDS A POLICY

Why render.logs needs a policy

This tool retrieves and queries service logs without creating, modifying, or deleting data. Log retrieval is a read-only operation with minimal blast radius if misused by an AI agent, as logs are meant to be inspected and typically contain only observational data about system behavior.

From the tool's definition Tool name 'render.logs' with description 'Get service logs' indicates retrieval of existing log data with no modification or side effects.

Attacks that exploit this kind of access

Questions about render.logs

What does the render.logs tool do? +

Get service logs. It is categorised as a Read tool in the MCP Fullstack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on render.logs? +

Register the MCP Fullstack MCP server in PolicyLayer and add a rule for render.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 MCP Fullstack. Nothing to install.

What risk level is render.logs? +

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

Can I rate-limit render.logs? +

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

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

render.logs is provided by the MCP Fullstack MCP server (jacobfv/mcp-fullstack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.