my_instances

List your subscribed runnable agent instances. These are the correct targets for real agent chats. Paused instances are omitted unless include_paused is true.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/my-instances.md

WHAT IT DOES

What my_instances does on ProAgentStore

AI agents call my_instances 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.

RISK

Why my_instances is rated Low

Retrieves metadata about user's agent instances without modification or execution.

From the tool's definition List your subscribed runnable agent instances. Paused instances are omitted.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs my_instances 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 my_instances, this is the rule to start with:

my_instances Allowed

my_instances is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "my_instances": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every my_instances call is checked against it from then on.

FAQ

Questions about my_instances

What does the my_instances tool do? +

List your subscribed runnable agent instances. These are the correct targets for real agent chats. Paused instances are omitted unless include_paused is true. It is categorised as a Read tool in the ProAgentStore MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on my_instances? +

Register the ProAgentStore MCP server in PolicyLayer and add a rule for my_instances: 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 my_instances? +

my_instances is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit my_instances? +

Yes. Add a rate_limit block to the my_instances 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 my_instances completely? +

Set action: deny in the PolicyLayer policy for my_instances. 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 my_instances? +

my_instances 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.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →