Check if an identifier name is consistent with existing naming patterns.
AI agents call check_consistency to retrieve information from MCP Pyrefly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a passive analysis of naming conventions by comparing an identifier against existing patterns. It retrieves information and provides feedback but has no side effects, code execution capability, or data modification. It fits the 'Read' category as a pure query/check operation.
From the tool's definition Tool name 'check_consistency' combined with description 'Check if an identifier name is consistent with existing naming patterns' indicates a read-only query operation that analyzes and reports on code properties without modifying, executing, or deleting…
Attacks that exploit this kind of access
Check if an identifier name is consistent with existing naming patterns. It is categorised as a Read tool in the MCP Pyrefly MCP Server, which means it retrieves data without modifying state.
Register the MCP Pyrefly MCP server in PolicyLayer and add a rule for check_consistency: 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 Pyrefly. Nothing to install.
check_consistency 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 check_consistency 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 check_consistency. 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.
check_consistency is provided by the MCP Pyrefly MCP server (kimasplund/mcp-pyrefly). 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 →