list_harness_stores

List local agent-harness session stores (opencode, kilocode, zed, delta, antigravity, cursor, vscode, codex): paths, presence, and format notes. Read-only; never touches harness processes.

SERVERProject Guardian MCP SOURCE1999azzar/project-guardian-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/1999azzar-project-guardian-mcp-server/list-harness-stores.md

WHAT IT DOES

What list_harness_stores does on Project Guardian MCP

AI agents call list_harness_stores to retrieve information from Project Guardian MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_harness_stores is rated Low

Tool retrieves session store information without modifying data or executing operations.

From the tool's definition List local agent-harness session stores; Read-only; never touches harness processes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_harness_stores safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_harness_stores, this is the rule to start with:

list_harness_stores Allowed

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

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

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

FAQ

Questions about list_harness_stores

What does the list_harness_stores tool do? +

List local agent-harness session stores (opencode, kilocode, zed, delta, antigravity, cursor, vscode, codex): paths, presence, and format notes. Read-only; never touches harness processes. It is categorised as a Read tool in the Project Guardian MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_harness_stores? +

Register the Project Guardian MCP server in PolicyLayer and add a rule for list_harness_stores: 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 Project Guardian MCP. Nothing to install.

What risk level is list_harness_stores? +

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

Can I rate-limit list_harness_stores? +

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

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

list_harness_stores is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Project Guardian, and thousands of servers like it.

This server

All 38 Project Guardian tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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