Get system logs for a specific lead, with optional offset and limit for pagination.
AI agents call getSystemLogs to retrieve information from Lofty MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system logs associated with a lead—a pure query operation. There is no data creation, modification, deletion, code execution, or financial impact. The only action is fetching logs for informational purposes, which is the classic read operation.
From the tool's definition Tool name 'getSystemLogs' and description 'Get system logs for a specific lead' indicate retrieval of existing data with no modification or side effects. Pagination parameters (offset, limit) are standard read-only query parameters.
Attacks that exploit this kind of access
Get system logs for a specific lead, with optional offset and limit for pagination. It is categorised as a Read tool in the Lofty MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for getSystemLogs: 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 Lofty MCP Server. Nothing to install.
getSystemLogs 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 getSystemLogs 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 getSystemLogs. 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.
getSystemLogs is provided by the Lofty MCP Server MCP server (nerdsnipe-inc/lofty-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →