This record as markdown: /tools/io-github-devopam-mcpg/lint-naming-conventions.md
What lint_naming_conventions does on Mcpg
AI agents call lint_naming_conventions to retrieve information from Mcpg without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why lint_naming_conventions is rated Low
Linting is a read-only analysis operation that checks code or schema against style rules without modifying or executing anything. The tool retrieves or validates existing naming conventions, making it a Read category operation with low severity since it has no side effects on data or system state.
From the tool's definition Tool name 'lint_naming_conventions' suggests static analysis or validation of naming patterns. No destructive, write, execute, or financial operations implied. The empty description prevents higher confidence.
Attacks that exploit this kind of access
The rule that runs lint_naming_conventions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For lint_naming_conventions, this is the rule to start with:
lint_naming_conventions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every lint_naming_conventions call is checked against it from then on.
Questions about lint_naming_conventions
lint_naming_conventions is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.
Register the Mcpg MCP server in PolicyLayer and add a rule for lint_naming_conventions: 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 Mcpg. Nothing to install.
lint_naming_conventions 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 lint_naming_conventions 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 lint_naming_conventions. 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.
lint_naming_conventions is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue