get_instance_connection_guide
The ready-made briefing for driving ONE instance: its id, its agent type, its registered repos, the tools it actually exposes with their exact field names, and a worked call_instance_tool example using its real names. Plain Markdown — paste it into another assistant
This record as markdown: /tools/io-github-proagentstore-platform/get-instance-connection-guide.md
What get_instance_connection_guide does on ProAgentStore
AI agents call get_instance_connection_guide to retrieve information from ProAgentStore without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_instance_connection_guide is rated Low
Reads configuration and structural data about instances and their tools; enables informed tool misuse if shared inappropriately.
From the tool's definition retrieves instance connection guide, id, agent type, repos, tools, field names
Attacks that exploit this kind of access
The rule that runs get_instance_connection_guide 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 get_instance_connection_guide, this is the rule to start with:
get_instance_connection_guide is read-only, so it stays allowed. 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 get_instance_connection_guide call is checked against it from then on.
Questions about get_instance_connection_guide
The ready-made briefing for driving ONE instance: its id, its agent type, its registered repos, the tools it actually exposes with their exact field names, and a worked call_instance_tool example using its real names. Plain Markdown — paste it into another assistant. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for get_instance_connection_guide: 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.
get_instance_connection_guide 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_instance_connection_guide 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_instance_connection_guide. 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_instance_connection_guide 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.
This server
Across the catalogue