Get the naming series information for a DocType
AI agents call get_naming_info to retrieve information from Frappe MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schema/configuration metadata about how documents are named in a Frappe DocType. It performs no creation, modification, deletion, or execution of code. It is purely informational and safe for an AI agent to call without risk of unintended data loss or state changes. Classified as Read with low severity.
From the tool's definition Tool description states 'Get the naming series information for a DocType' — a retrieval operation with no modification or side effects. The verb 'Get' and the readonly nature of retrieving metadata about naming conventions indicate a read-only query.
Attacks that exploit this kind of access
Get the naming series information for a DocType. It is categorised as a Read tool in the Frappe MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Frappe MCP Server MCP server in PolicyLayer and add a rule for get_naming_info: 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 Frappe MCP Server. Nothing to install.
get_naming_info 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 get_naming_info 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 get_naming_info. 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.
get_naming_info is provided by the Frappe MCP Server MCP server (kiran-harbak/frappe_mcp_server). 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 →