test_instance_mcp_server
Connect to a remote MCP endpoint as this instance would and report what is actually true about it: whether it answered, what tools it publishes, and for each tool whether this agent could really CALL it — naming which of the three gates (the agent
This record as markdown: /tools/io-github-proagentstore-platform/test-instance-mcp-server.md
What test_instance_mcp_server does on ProAgentStore
AI agents invoke test_instance_mcp_server to trigger actions in ProAgentStore. 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 test_instance_mcp_server is rated High
Tool actively connects to remote endpoints and tests live tool invocations, triggering external operations.
From the tool's definition Connect to a remote MCP endpoint... call it — naming which of the three gates
Attacks that exploit this kind of access
The rule that runs test_instance_mcp_server safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For test_instance_mcp_server, this is the rule to start with:
test_instance_mcp_server 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 ProAgentStore, apply this rule, and every test_instance_mcp_server call is checked against it from then on.
Questions about test_instance_mcp_server
Connect to a remote MCP endpoint as this instance would and report what is actually true about it: whether it answered, what tools it publishes, and for each tool whether this agent could really CALL it — naming which of the three gates (the agent. It is categorised as a Execute tool in the ProAgentStore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for test_instance_mcp_server: 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 ProAgentStore. Nothing to install.
test_instance_mcp_server 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 test_instance_mcp_server 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 test_instance_mcp_server. 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.
test_instance_mcp_server is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
Across the catalogue