ingest_repo_status

List the repositories indexed on a repo-chat instance and each one

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/ingest-repo-status.md

WHAT IT DOES

What ingest_repo_status does on ProAgentStore

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

The tool lists existing indexed repositories and their status—a pure read operation that retrieves information without modifying, deleting, or executing operations. The verb 'List' and the passive observation of 'indexed' repositories confirm this is a Read category tool with low severity due to minimal blast radius if misused.

From the tool's definition Tool name 'ingest_repo_status' and description 'List the repositories indexed on a repo-chat instance' indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ingest_repo_status Allowed

ingest_repo_status 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": {
    "ingest_repo_status": {}
  }
}

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 ingest_repo_status call is checked against it from then on.

FAQ

Questions about ingest_repo_status

What does the ingest_repo_status tool do? +

List the repositories indexed on a repo-chat instance and each one. 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 ingest_repo_status? +

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

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

Can I rate-limit ingest_repo_status? +

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

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

ingest_repo_status 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

editor_status on 010 Editor → The MCP Attack Database →

Guides

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