list_integrations

THE RISK

Low Risk

Why list_integrations needs a policy

This tool queries and returns existing integration configurations without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves information about project integrations. The low severity reflects that listing integrations poses minimal risk—it only exposes configuration metadata without enabling changes or harmful actions.

From the tool's definition Tool name 'list_integrations' and description 'List all configured integrations for a project' indicate a pure retrieval operation with no side effects.

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

POLICY

How to control list_integrations

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

policy.json

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

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

Create a free account and register MCP Server for Coroot — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP Server for Coroot tools

Destructive delete_api_key Delete an API key. Destructive delete_application_category Delete an application category. Destructive delete_custom_cloud_pricing Delete custom cloud pricing configuration. Destructive delete_dashboard Delete a custom dashboard. Destructive delete_integration Delete an integration configuration. Destructive delete_project Delete a project and all associated data. Execute test_integration Test an integration configuration. Write configure_integration configure_integration

All 61 MCP Server for Coroot tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_integrations

What does the list_integrations tool do? +

List all configured integrations for a project. It is categorised as a Read tool in the MCP Server for Coroot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_integrations? +

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

What risk level is list_integrations? +

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

Can I rate-limit list_integrations? +

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

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

list_integrations is provided by the MCP Server for Coroot MCP server (jamesbrink/mcp-coroot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Server for Coroot tool call.

Start from MCP Server for Coroot, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →