New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

list_source_control_connections

List source-control connections with repository binding count, last durably acknowledged delivery, rejection state, actionable health, and the exact webhook events that are safe to enable.

SERVERAdrata SOURCE@adrata/adrata-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-adrata-mcp/list-source-control-connections.md

What list_source_control_connections does on Adrata

AI agents call list_source_control_connections to retrieve information from Adrata without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_source_control_connections is rated Low

Even though list_source_control_connections only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about list_source_control_connections

What does the list_source_control_connections tool do? +

List source-control connections with repository binding count, last durably acknowledged delivery, rejection state, actionable health, and the exact webhook events that are safe to enable. It is categorised as a Read tool in the Adrata MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_source_control_connections? +

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

What risk level is list_source_control_connections? +

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

Can I rate-limit list_source_control_connections? +

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

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

list_source_control_connections is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Adrata, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Adrata's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.