edgeconnect_run_link_integrity_test
Start an EdgeConnect link-integrity iperf/tcpperf test with write guards.
This record as markdown: /tools/secure-ssid-centralmcp/edgeconnect-run-link-integrity-test.md
What edgeconnect_run_link_integrity_test does on API-Central
AI agents invoke edgeconnect_run_link_integrity_test to trigger actions in API-Central. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why edgeconnect_run_link_integrity_test is rated High
This tool triggers execution of network performance testing commands (iperf/tcpperf) on EdgeConnect infrastructure. While not destructive and not creating permanent configuration changes, it executes external diagnostic operations whose effects depend on network state and target selection. The 'write guards' mitigate but do not eliminate the Execute classification.
From the tool's definition Tool name contains 'run' and description states 'Start an EdgeConnect link-integrity iperf/tcpperf test' — these are active operations that execute network diagnostic commands on infrastructure.
Attacks that exploit this kind of access
The rule that runs edgeconnect_run_link_integrity_test 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 edgeconnect_run_link_integrity_test, this is the rule to start with:
edgeconnect_run_link_integrity_test stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 edgeconnect_run_link_integrity_test call is checked against it from then on.
Questions about edgeconnect_run_link_integrity_test
Start an EdgeConnect link-integrity iperf/tcpperf test with write guards. It is categorised as a Execute tool in the API-Central MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the API-Central MCP server in PolicyLayer and add a rule for edgeconnect_run_link_integrity_test: 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.
edgeconnect_run_link_integrity_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the edgeconnect_run_link_integrity_test 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 edgeconnect_run_link_integrity_test. 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.
edgeconnect_run_link_integrity_test 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.
Across the catalogue