New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

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

Questions about test_instance_mcp_server

What does the test_instance_mcp_server tool do? +

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.

How do I enforce a policy on test_instance_mcp_server? +

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.

What risk level is test_instance_mcp_server? +

test_instance_mcp_server is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_instance_mcp_server? +

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.

How do I block test_instance_mcp_server completely? +

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.

What MCP server provides test_instance_mcp_server? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ProAgentStore's. Pull the full record:

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.