recent_instances

The instances THIS account is driving or drove most recently over MCP, each with its latest run

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/recent-instances.md

WHAT IT DOES

What recent_instances does on ProAgentStore

AI agents call recent_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 recent_instances is rated Low

Retrieves recent instance activity data; no modifications or side effects.

From the tool's definition instances THIS account is driving or drove most recently

Attacks that exploit this kind of access

RECOMMENDED RULE

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

recent_instances Allowed

recent_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": {
    "recent_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 recent_instances call is checked against it from then on.

FAQ

Questions about recent_instances

What does the recent_instances tool do? +

The instances THIS account is driving or drove most recently over MCP, each with its latest run. 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 recent_instances? +

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

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

Can I rate-limit recent_instances? +

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

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

recent_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 →