Purpose: Get detailed information about a specific API request log, including the full request and response bodies. Returns: Log details: id, created_at, endpoint, method, response_status, user_agent, request_body, response_body. When to use: - User wants to inspect a specific API request - Debug...
AI agents call get-log to retrieve information from Email Sending MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that fetches diagnostic log data. While logs may contain sensitive information like request/response bodies, the tool itself performs no write, execute, destructive, or financial operations. The severity is low because viewing logs is a standard debugging activity with no capability to alter system state or data.
From the tool's definition The tool retrieves and displays log information ("Get detailed information", "Returns: Log details: id, created_at, endpoint, method, response_status, user_agent, request_body, response_body").
Documented attack patterns abuse exactly the kind of access get-log gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Email Sending MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get-log:
{
"version": "1",
"default": "deny",
"tools": {
"get-log": {}
}
}get-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.
Purpose: Get detailed information about a specific API request log, including the full request and response bodies. Returns: Log details: id, created_at, endpoint, method, response_status, user_agent, request_body, response_body. When to use: - User wants to inspect a specific API request - Debugging a particular API call - User says. It is categorised as a Read tool in the Email Sending MCP MCP Server, which means it retrieves data without modifying state.
Register the Email Sending MCP server in PolicyLayer and add a rule for get-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 Email Sending MCP. Nothing to install.
get-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 get-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 get-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.
get-log is provided by the Email Sending MCP server (resend/resend-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 77 Email Sending MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
77 Email Sending MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.