AI agents call list_files to retrieve information from UOFastMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a basic listing/enumeration operation with no side effects. It queries available files but does not create, modify, delete, or execute any code. The blast radius is minimal—an agent listing files cannot cause data loss or unauthorized changes. The presence of RBAC and audit logging on the server further mitigates risk by controlling access.
From the tool's definition Tool name 'list_files' and description 'List available files in the current Unidata account' indicate a read-only operation that retrieves directory or file metadata without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List available files in the current Unidata account. It is categorised as a Read tool in the UOFastMCP MCP Server, which means it retrieves data without modifying state.
Register the UOFast MCP server in PolicyLayer and add a rule for list_files: 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 UOFastMCP. Nothing to install.
list_files 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_files 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_files. 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_files is provided by the UOFast MCP server (rokipark/uofastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
list_files is one line of UOFast's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →