get_csrf_token
A read tool on the NapCat MCP server.
This record as markdown: /tools/1021143806-napcat-mcp/get-csrf-token.md
What get_csrf_token does on NapCat MCP Server
AI agents call get_csrf_token to retrieve information from NapCat MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_csrf_token is rated Low
The tool retrieves a CSRF token, which is informational data used for security purposes. While not modifying data directly, obtaining security tokens can enable subsequent attacks if misused by an agent (e.g., to craft authenticated requests for destructive operations). However, the tool itself only reads/retrieves the token.
From the tool's definition Tool name 'get_csrf_token' and description 'Get CSRF token' indicate retrieval of a security token with no direct data modification or deletion. This is a read operation that queries/retrieves credentials.
Attacks that exploit this kind of access
The rule that runs get_csrf_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and NapCat MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_csrf_token, this is the rule to start with:
get_csrf_token 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 NapCat MCP Server, apply this rule, and every get_csrf_token call is checked against it from then on.
Questions about get_csrf_token
get_csrf_token is a read tool on the NapCat MCP Server MCP server. It is categorised as a Read tool in the NapCat MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NapCat MCP Server MCP server in PolicyLayer and add a rule for get_csrf_token: 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 NapCat MCP Server. Nothing to install.
get_csrf_token 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_csrf_token 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_csrf_token. 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_csrf_token is provided by the NapCat MCP Server MCP server (1021143806/napcat_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on NapCat MCP Server, and thousands of servers like it.
This server
Across the catalogue