List all available connectors offered by Pica and connections in the user
AI agents call list_user_connections_and_available_connectors to retrieve information from Pica MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing connectors and user connections. It has no side effects, does not modify data, does not execute actions, and does not involve financial operations. It is a straightforward read operation that gathers information about available integrations and existing connections.
From the tool's definition Tool name contains 'list' and description states 'List all available connectors... and connections in the user' — purely retrieval operations with no modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
List all available connectors offered by Pica and connections in the user. It is categorised as a Read tool in the Pica MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pica MCP Server MCP server in PolicyLayer and add a rule for list_user_connections_and_available_connectors: 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 Pica MCP Server. Nothing to install.
list_user_connections_and_available_connectors 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_user_connections_and_available_connectors 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_user_connections_and_available_connectors. 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_user_connections_and_available_connectors is provided by the Pica MCP Server MCP server (moekatib/pica-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 →