get_connector_calls

Raw connector call log. Filter by connector name, action, or success.

Server Copilot Insights MCP Server syokiel/copilot-insights
Category Read
Risk class Low
Parameters 00 required

What get_connector_calls does on Copilot Insights MCP Server

AI agents call get_connector_calls to retrieve information from Copilot Insights MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_connector_calls needs a policy

The tool retrieves and filters existing telemetry logs without creating, modifying, deleting, or executing operations. The severity is medium rather than low because the connector call logs may contain sensitive information about system interactions, user behavior patterns, and connector configurations that could be misused if queried without proper authorization, but the tool itself performs no destructive or…

From the tool's definition Tool description states 'Raw connector call log. Filter by connector name, action, or success.' — this is a query/filter operation on telemetry data with no modification or execution capabilities.

Questions about get_connector_calls

What does the get_connector_calls tool do? +

Raw connector call log. Filter by connector name, action, or success. It is categorised as a Read tool in the Copilot Insights MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_connector_calls? +

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

What risk level is get_connector_calls? +

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

Can I rate-limit get_connector_calls? +

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

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

get_connector_calls is provided by the Copilot Insights MCP Server MCP server (syokiel/copilot-insights). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.