AI agents call list_eff_resources to retrieve information from Eff without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple listing/discovery tool that queries and returns metadata about available resources. It has no side effects, does not execute code or commands, does not modify data, and does not delete anything. It is purely informational and falls squarely into the Read category with low severity.
From the tool's definition Tool name 'list_eff_resources' and description 'List available EFF MCP resources and their descriptions' indicate a read-only operation that retrieves and displays information without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
List available EFF MCP resources and their descriptions. It is categorised as a Read tool in the Eff MCP Server, which means it retrieves data without modifying state.
Register the Eff MCP server in PolicyLayer and add a rule for list_eff_resources: 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 Eff. Nothing to install.
list_eff_resources 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_eff_resources 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_eff_resources. 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_eff_resources is provided by the Eff MCP server (vs3kulic/eff-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 →