smell_detect_god_classes

Find classes with too many responsibilities that violate the Single Responsibility Principle

SERVERPlugin Hub SOURCE@barnburner121/plugin-hub-mcp

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/barnburner121-plugin-hub-mcp/smell-detect-god-classes.md

WHAT IT DOES

What smell_detect_god_classes does on Plugin Hub

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

RISK

Why smell_detect_god_classes is rated Low

Even though smell_detect_god_classes only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs smell_detect_god_classes safely

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

smell_detect_god_classes Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Plugin Hub, apply this rule, and every smell_detect_god_classes call is checked against it from then on.

FAQ

Questions about smell_detect_god_classes

What does the smell_detect_god_classes tool do? +

Find classes with too many responsibilities that violate the Single Responsibility Principle. It is categorised as a Read tool in the Plugin Hub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on smell_detect_god_classes? +

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

What risk level is smell_detect_god_classes? +

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

Can I rate-limit smell_detect_god_classes? +

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

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

smell_detect_god_classes is provided by the Plugin Hub MCP server (@barnburner121/plugin-hub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Plugin Hub, and thousands of servers like it.

This server

All 616 Plugin Hub tools →

Across the catalogue

The MCP Attack Database →

Guides

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