Low Risk

folderAgentGet

Get agents in a folder.

How to control folderAgentGet ↓

AI agents call folderAgentGet to retrieve information from Mcp Taskade without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries or retrieves a list of agents contained within a folder. It performs no modifications, deletions, or external executions. The operation is read-only and has no blast radius beyond information disclosure.

From the tool's definition Tool name 'folderAgentGet' and description 'Get agents in a folder' indicate a retrieval operation with no side effects. The verb 'Get' is a clear read operation.

Documented attack patterns abuse exactly the kind of access folderAgentGet gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Taskade, and nothing reaches the server without passing your rules. This is the rule we recommend for folderAgentGet:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "folderAgentGet": {}
  }
}

folderAgentGet is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Taskade — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the folderAgentGet tool do? +

Get agents in a folder. It is categorised as a Read tool in the Mcp Taskade MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on folderAgentGet? +

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

What risk level is folderAgentGet? +

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

Can I rate-limit folderAgentGet? +

Yes. Add a rate_limit block to the folderAgentGet 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 folderAgentGet completely? +

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

folderAgentGet is provided by the Mcp Taskade MCP server (taskade/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Taskade tool call.

Deterministic rules across all 57 Mcp Taskade tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

57 Mcp Taskade tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.