openspec_list_cross_service_docs

THE RISK

Low Risk

Why openspec_list_cross_service_docs needs a policy

This tool queries and retrieves existing cross-service documentation associated with a change proposal. It has no side effects, does not modify state, and does not execute code or trigger external operations. It is a straightforward read operation that falls clearly within the Read category with low severity.

From the tool's definition Tool name contains 'list' and description states 'Returns documents defined in proposal.md frontmatter crossService config' — a pure data retrieval operation with no modification, deletion, or execution capability.

Documented attack patterns abuse exactly the kind of access openspec_list_cross_service_docs gives an agent:

POLICY

How to control openspec_list_cross_service_docs

PolicyLayer is an MCP gateway — it sits between your AI agents and OpenSpec MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for openspec_list_cross_service_docs:

policy.json

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

openspec_list_cross_service_docs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register OpenSpec MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OpenSpec MCP tools

Execute openspec_setup_hooks Install or uninstall OpenSpec Git hooks Write openspec_record_revision Record a design revision when fixing bugs or adjusting design that deviates from the origi Write openspec_reply_review Reply to a review comment Write openspec_request_approval Request approval for a change Write openspec_sync_revisions Sync recorded revisions to design.md or proposal.md before archiving Write openspec_add_review Add a review comment to a change or spec Write openspec_approve_change Approve a change Write openspec_archive_change Archive a completed change proposal. Automatically syncs revisions to design.md before arc

All 40 OpenSpec MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about openspec_list_cross_service_docs

What does the openspec_list_cross_service_docs tool do? +

List cross-service documents for a change proposal. Returns documents defined in proposal.md frontmatter crossService config. It is categorised as a Read tool in the OpenSpec MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on openspec_list_cross_service_docs? +

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

What risk level is openspec_list_cross_service_docs? +

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

Can I rate-limit openspec_list_cross_service_docs? +

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

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

openspec_list_cross_service_docs is provided by the OpenSpec MCP server (lumiaqian/openspec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OpenSpec MCP tool call.

Start from OpenSpec MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →