This record as markdown: /tools/com-files-python-mcp/list-sync-log.md
What List_Sync_Log does on Files Com
AI agents call List_Sync_Log to retrieve information from Files Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why List_Sync_Log is rated Low
This tool retrieves or queries sync log data from the Files.com environment without modifying, deleting, or executing operations. It has no side effects and follows the read category pattern of listing/fetching existing information. The low severity reflects minimal blast radius—an AI agent misusing this would only gain visibility into sync logs, not alter system state or access sensitive operations.
From the tool's definition Tool name 'List_Sync_Log' and description 'List Sync Logs' indicate data retrieval with 'List' verb, which is a read-only query operation.
Attacks that exploit this kind of access
The rule that runs List_Sync_Log safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Files Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For List_Sync_Log, this is the rule to start with:
List_Sync_Log 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 Files Com, apply this rule, and every List_Sync_Log call is checked against it from then on.
Questions about List_Sync_Log
List Sync Logs. It is categorised as a Read tool in the Files Com MCP Server, which means it retrieves data without modifying state.
Register the Files Com MCP server in PolicyLayer and add a rule for List_Sync_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 Files Com. Nothing to install.
List_Sync_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 List_Sync_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 List_Sync_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.
List_Sync_Log is provided by the Files Com MCP server (files-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Files Com, and thousands of servers like it.
This server
Across the catalogue