Low Risk

search_issues

Searches for issues in SpaceBridge. Always define project slug. Use similarity search for best results.

How to control search_issues ↓

What search_issues does on SpaceBridge-MCP

AI agents call search_issues to retrieve information from SpaceBridge-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why search_issues needs a policy

This tool retrieves or queries existing issues from the issue tracker with no side effects. It matches the 'Read' category pattern (search, list, get, fetch) and poses minimal risk if misused by an AI agent—worst case, it returns unwanted search results. No data is created, modified, deleted, or irreversibly changed.

From the tool's definition Tool name 'search_issues' and description 'Searches for issues in SpaceBridge' indicate a query operation that retrieves data without modification.

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

How to control search_issues

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_issues": {}
  }
}

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

  1. Create a free account and register SpaceBridge-MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about search_issues

What does the search_issues tool do? +

Searches for issues in SpaceBridge. Always define project slug. Use similarity search for best results. It is categorised as a Read tool in the SpaceBridge-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_issues? +

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

What risk level is search_issues? +

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

Can I rate-limit search_issues? +

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

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

search_issues is provided by the SpaceBridge- MCP server (spacecode-ai/spacebridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SpaceBridge-MCP tool call.

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

Free to start. No card required.

4 SpaceBridge-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.