call_files
Lista las grabaciones y transcripts de todas las llamadas — archivos permanentes en EasyBits Files, disponibles aunque la VM ya se haya destruido. Retorna [{ id, name, url, source, createdAt }].
This record as markdown: /tools/cloud-easybits-easybits/call-files.md
What call_files does on EasyBits
AI agents use call_files to create or update resources in EasyBits, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EasyBits environment.
Why call_files is rated Medium
An AI agent can call call_files faster than any human can review: one bad instruction and it creates or modifies resources in EasyBits by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs call_files safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For call_files, this is the rule to start with:
call_files stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every call_files call is checked against it from then on.
Questions about call_files
Lista las grabaciones y transcripts de todas las llamadas — archivos permanentes en EasyBits Files, disponibles aunque la VM ya se haya destruido. Retorna [{ id, name, url, source, createdAt }]. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EasyBits MCP server in PolicyLayer and add a rule for call_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 EasyBits. Nothing to install.
call_files is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the call_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 call_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.
call_files is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue