app_list_documents

A read tool on the Eda Agent MCP server.

SERVEREda Agent SOURCEsalitronic/eda-agent

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eda-agent/app-list-documents.md

WHAT IT DOES

What app_list_documents does on Eda Agent

AI agents call app_list_documents to retrieve information from Eda Agent without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why app_list_documents is rated Low

The tool appears to query and return a list of documents without modifying state, deleting data, executing code, or moving money. The naming pattern aligns with read operations (list, get, fetch). Confidence is slightly lowered due to empty description, but the 'list_' prefix is conventionally associated with read operations in most APIs.

From the tool's definition Tool name 'app_list_documents' implies retrieval/enumeration of documents. No description provided, but the 'list' verb and context within a design automation server (alongside query/get operations) strongly suggests read-only data retrieval.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs app_list_documents safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Eda Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For app_list_documents, this is the rule to start with:

app_list_documents Allowed

app_list_documents is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "app_list_documents": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every app_list_documents call is checked against it from then on.

FAQ

Questions about app_list_documents

What does the app_list_documents tool do? +

app_list_documents is a read tool on the Eda Agent MCP server. It is categorised as a Read tool in the Eda Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on app_list_documents? +

Register the Eda Agent MCP server in PolicyLayer and add a rule for app_list_documents: 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 Eda Agent. Nothing to install.

What risk level is app_list_documents? +

app_list_documents is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit app_list_documents? +

Yes. Add a rate_limit block to the app_list_documents 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.

How do I block app_list_documents completely? +

Set action: deny in the PolicyLayer policy for app_list_documents. 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.

What MCP server provides app_list_documents? +

app_list_documents is provided by the Eda Agent MCP server (salitronic/eda-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Eda Agent, and thousands of servers like it.

This server

All 345 Eda Agent tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →