List client device/asset configurations from ConnectWise (live, not embedded).
AI agents call get_configurations to retrieve information from ConnectWise Live 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 existing configuration data about client devices and assets without creating, modifying, deleting, or executing any operations. It has minimal blast radius as misuse would only expose information the agent already has authorization to access in ConnectWise.
From the tool's definition Tool description states 'List client device/asset configurations' which is a retrieval operation with no modification or side effects. The verb 'List' and the scope ('from ConnectWise') indicate a query-only function.
Attacks that exploit this kind of access
List client device/asset configurations from ConnectWise (live, not embedded). It is categorised as a Read tool in the ConnectWise Live MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ConnectWise Live MCP Server MCP server in PolicyLayer and add a rule for get_configurations: 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 ConnectWise Live MCP Server. Nothing to install.
get_configurations 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 get_configurations 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 get_configurations. 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.
get_configurations is provided by the ConnectWise Live MCP Server MCP server (mfrostbutter/connectwise-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 →