Analyzes code for SOLID principles compliance and suggests improvements
AI agents call solid_analyzer to retrieve information from MCP Project Orchestrator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs static code analysis and returns suggestions. It retrieves and examines code to provide feedback, which is a read-only operation with no side effects on data, infrastructure, or systems. No code is executed, modified, or deleted. The blast radius of misuse is minimal — an AI could at worst analyze sensitive code it shouldn't see, but cannot modify, delete, or trigger external operations.
From the tool's definition Tool description states it 'analyzes code for SOLID principles compliance and suggests improvements' — a pure analysis/inspection operation with no mutation, deletion, or execution of external systems.
Documented attack patterns abuse exactly the kind of access solid_analyzer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Project Orchestrator, and nothing reaches the server without passing your rules. This is the rule we recommend for solid_analyzer:
{
"version": "1",
"default": "deny",
"tools": {
"solid_analyzer": {}
}
}solid_analyzer is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyzes code for SOLID principles compliance and suggests improvements. It is categorised as a Read tool in the MCP Project Orchestrator MCP Server, which means it retrieves data without modifying state.
Register the MCP Project Orchestrator MCP server in PolicyLayer and add a rule for solid_analyzer: 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 Project Orchestrator. Nothing to install.
solid_analyzer is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the solid_analyzer 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.
Set action: deny in the PolicyLayer policy for solid_analyzer. 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.
solid_analyzer is provided by the MCP Project Orchestrator MCP server (sparesparrow/mcp-project-orchestrator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Project Orchestrator, 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.
15 MCP Project Orchestrator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.