uxi_assign_service_test_to_group
Assign a UXI service test to a group; requires read-write access.
This record as markdown: /tools/secure-ssid-centralmcp/uxi-assign-service-test-to-group.md
What uxi_assign_service_test_to_group does on API-Central
AI agents use uxi_assign_service_test_to_group to create or update resources in API-Central, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your API-Central environment.
Why uxi_assign_service_test_to_group is rated Medium
This tool creates or modifies configurations (assigning tests to groups) without deleting data or executing arbitrary code. It is a reversible write operation on network monitoring infrastructure. Severity is medium because misconfiguration of UXI service tests could impact network monitoring visibility, but the blast radius is limited to test assignment scope, not widespread network operations or data destruction.
From the tool's definition Tool name contains 'assign' and description explicitly states 'requires read-write access', indicating modification of test assignments. The action creates or modifies the association between a UXI service test and a group.
Attacks that exploit this kind of access
The rule that runs uxi_assign_service_test_to_group safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API-Central, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For uxi_assign_service_test_to_group, this is the rule to start with:
uxi_assign_service_test_to_group stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect API-Central, apply this rule, and every uxi_assign_service_test_to_group call is checked against it from then on.
Questions about uxi_assign_service_test_to_group
Assign a UXI service test to a group; requires read-write access. It is categorised as a Write tool in the API-Central MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the API-Central MCP server in PolicyLayer and add a rule for uxi_assign_service_test_to_group: 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 API-Central. Nothing to install.
uxi_assign_service_test_to_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the uxi_assign_service_test_to_group 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 uxi_assign_service_test_to_group. 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.
uxi_assign_service_test_to_group is provided by the API-Central MCP server (secure-ssid/centralmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API-Central, and thousands of servers like it.
This server
Across the catalogue