Purpose: List API request logs for the account. Use to review recent API activity, debug issues, or audit API usage. Returns: For each log: id, created_at, endpoint, method, response_status, user_agent. Use pagination (limit, after/before) for large lists. When to use: - User wants to see recent ...
AI agents call list-logs 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 tool purely retrieves and queries existing log data without side effects. It enables read-only access to audit logs for debugging and monitoring purposes. The tool cannot execute commands, modify data, delete records, or perform financial operations.
From the tool's definition Tool description states 'List API request logs' and 'review recent API activity' with return values limited to id, created_at, endpoint, method, response_status, user_agent. No modification, deletion, or execution capabilities described.
Documented attack patterns abuse exactly the kind of access list-logs 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 list-logs:
{
"version": "1",
"default": "deny",
"tools": {
"list-logs": {}
}
}list-logs 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: List API request logs for the account. Use to review recent API activity, debug issues, or audit API usage. Returns: For each log: id, created_at, endpoint, method, response_status, user_agent. Use pagination (limit, after/before) for large lists. When to use: - User wants to see recent API activity - Debugging API issues or checking request history - 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 list-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 Email Sending MCP. Nothing to install.
list-logs 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 list-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.
Set action: deny in the PolicyLayer policy for list-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.
list-logs 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.