suggest_improvements
AI agents call suggest_improvements to retrieve information from Best Practices MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to analyze and suggest improvements to code, which is fundamentally a read operation—it retrieves or queries coding guidelines and generates suggestions without creating, modifying, or destructively changing any data. The server's stated purpose includes 'code review capabilities' and 'searchable guidelines,' positioning this as an informational read tool.
From the tool's definition Tool name 'suggest_improvements' combined with server context describing 'actionable improvement suggestions' and 'code review capabilities' indicates the tool retrieves and returns suggestions for code improvement without modifying data.
Attacks that exploit this kind of access
suggest_improvements. It is categorised as a Read tool in the Best Practices MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Best Practices MCP Server MCP server in PolicyLayer and add a rule for suggest_improvements: 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 Best Practices MCP Server. Nothing to install.
suggest_improvements 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 suggest_improvements 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 suggest_improvements. 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.
suggest_improvements is provided by the Best Practices MCP Server MCP server (n-ochs/best-practice-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →