list_fas
AI agents call list_fas to retrieve information from Frappe MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The server's read-only design and the tool's naming pattern (list_*) align with retrieving/querying data without side effects. FAS likely refers to Fixed Assets or similar ERP records. The absence of a description lowers confidence slightly, but the server-level read-only constraint and sibling tool patterns justify Read classification.
From the tool's definition Server is explicitly described as 'Read-only MCP server' and tool name 'list_fas' follows the pattern of sibling Read tools (list_assets, list_cois, frappe_list_docs). Description is empty, but context strongly indicates data retrieval.
Attacks that exploit this kind of access
list_fas. It is categorised as a Read tool in the Frappe MCP MCP Server, which means it retrieves data without modifying state.
Register the Frappe MCP server in PolicyLayer and add a rule for list_fas: 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. Nothing to install.
list_fas 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 list_fas 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 list_fas. 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.
list_fas is provided by the Frappe MCP server (tourscale-repos/frappe-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 →