sonar_rules_search

Busca reglas en SonarQube.

SERVERMCP Framework Personal SOURCEinggerman/mcps

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/inggerman-mcps/sonar-rules-search.md

WHAT IT DOES

What sonar_rules_search does on MCP Framework Personal

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

RISK

Why sonar_rules_search is rated Low

This tool performs a search query against SonarQube's rule database, returning information about static analysis rules. It is a read-only operation with no side effects, no code execution, and no data modification. The search operation is typical of Read category tools that retrieve or query data.

From the tool's definition Tool name 'sonar_rules_search' and description 'Busca reglas en SonarQube' (Search rules in SonarQube) indicates a query/search operation that retrieves rule information from SonarQube without modifying or executing code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sonar_rules_search safely

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

sonar_rules_search Allowed

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

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

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

FAQ

Questions about sonar_rules_search

What does the sonar_rules_search tool do? +

Busca reglas en SonarQube. It is categorised as a Read tool in the MCP Framework Personal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sonar_rules_search? +

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

What risk level is sonar_rules_search? +

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

Can I rate-limit sonar_rules_search? +

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

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

sonar_rules_search is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Framework Personal, and thousands of servers like it.

This server

All 811 MCP Framework Personal tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →search_circuits on 0gzk → The MCP Attack Database →

Guides

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