Low Risk

tascan_list_agents

List all registered AI agents with their capabilities, inbox IDs, and status. Like reading input labels on a video matrix — discover which agents are available and what they can do before dispatching work.

Part of the TaScan server.

tascan_list_agents is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TASCAN →

Free to start. No card required.

AI agents call tascan_list_agents to retrieve information from TaScan without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though tascan_list_agents only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full TaScan policy for all 32 tools.

Get this rule live on your own TaScan server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TASCAN →

View all 32 tools →

These attack patterns abuse exactly the kind of access tascan_list_agents gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so tascan_list_agents only ever does what you allow.

SECURE TASCAN →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the tascan_list_agents tool do? +

List all registered AI agents with their capabilities, inbox IDs, and status. Like reading input labels on a video matrix — discover which agents are available and what they can do before dispatching work.. It is categorised as a Read tool in the TaScan MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tascan_list_agents? +

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

What risk level is tascan_list_agents? +

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

Can I rate-limit tascan_list_agents? +

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

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

tascan_list_agents is provided by the TaScan MCP server (tascan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TaScan tool call.

Deterministic rules across all 32 TaScan tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.