sf_get_event_logs
Queries EventLogFile for detailed activity logs. Event logs capture granular org activity for security monitoring and performance analysis. Common eventType values: - Login — login attempts and results - API — SOAP/REST API calls - Report — report executions - Flow — Flow runs and executions - Ap...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-get-event-logs.md
What sf_get_event_logs does on Salesforce Metadata Mcp
AI agents call sf_get_event_logs to retrieve information from Salesforce Metadata Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why sf_get_event_logs is rated Low
This tool retrieves security and activity log data from Salesforce's EventLogFile object. It is fundamentally a read operation that queries existing logs for monitoring purposes. While logs can contain sensitive information (logins, API calls, code executions), the tool itself only accesses data without side effects.
From the tool's definition Queries EventLogFile for detailed activity logs capturing org activity including login attempts, API calls, Apex executions, and page views. The tool retrieves and returns parsed CSV log entries without modification or deletion.
Attacks that exploit this kind of access
The rule that runs sf_get_event_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_get_event_logs, this is the rule to start with:
sf_get_event_logs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_get_event_logs call is checked against it from then on.
Questions about sf_get_event_logs
Queries EventLogFile for detailed activity logs. Event logs capture granular org activity for security monitoring and performance analysis. Common eventType values: - Login — login attempts and results - API — SOAP/REST API calls - Report — report executions - Flow — Flow runs and executions - ApexExecution — Apex code executions - LightningPageView — Lightning page views - RestApi — REST API requests - VisualforceRequest — Visualforce page requests - URI — general HTTP requests - LightningError — Lightning component errors Returns parsed CSV log entries (up to 20 rows per log file, up to 3 files per call). Requires Event Monitoring add-on OR Agentforce debug logs to be enabled. It is categorised as a Read tool in the Salesforce Metadata Mcp MCP Server, which means it retrieves data without modifying state.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_get_event_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 Metadata Mcp. Nothing to install.
sf_get_event_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 sf_get_event_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 sf_get_event_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.
sf_get_event_logs is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Salesforce Metadata, and thousands of servers like it.
This server
Across the catalogue