AI agents call get_debug_logs to retrieve information from Salesforce without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries debug logs from Salesforce without creating, modifying, or deleting data. It is a pure read operation that has no capability to alter system state or trigger external actions. The blast radius of misuse is minimal—an agent could only access log information that may already be visible within the Salesforce environment or restricted by permissions.
From the tool's definition Tool name 'get_debug_logs' and description 'Get recent debug logs' indicate retrieval of existing log data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_debug_logs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Salesforce, and nothing reaches the server without passing your rules. This is the rule we recommend for get_debug_logs:
{
"version": "1",
"default": "deny",
"tools": {
"get_debug_logs": {}
}
}get_debug_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.
Get recent debug logs. It is categorised as a Read tool in the Salesforce MCP Server, which means it retrieves data without modifying state.
Register the Salesforce MCP server in PolicyLayer and add a rule for get_debug_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 Salesforce. Nothing to install.
get_debug_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 get_debug_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 get_debug_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.
get_debug_logs is provided by the Salesforce MCP server (ryu-727/salesforce-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Salesforce, 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.
25 Salesforce tools catalogued and risk-classified — across an index of 43,000+ MCP servers.