configure_napkin_api_key
Configure the Napkin AI API key for this session.
This record as markdown: /tools/freshdesk/configure-napkin-api-key.md
What configure_napkin_api_key does on Freshdesk
AI agents use configure_napkin_api_key to create or update resources in Freshdesk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshdesk environment.
Why configure_napkin_api_key is rated Medium
This tool creates or modifies configuration settings (API key storage) within the session scope, making it a Write operation. While it doesn't directly access user data, improper configuration could affect downstream API behavior or logging.
From the tool's definition Tool name: 'configure_napkin_api_key'; description states it configures/sets an API key 'for this session', which modifies session configuration state.
Attacks that exploit this kind of access
The rule that runs configure_napkin_api_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For configure_napkin_api_key, this is the rule to start with:
configure_napkin_api_key stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every configure_napkin_api_key call is checked against it from then on.
Questions about configure_napkin_api_key
Configure the Napkin AI API key for this session. It is categorised as a Write tool in the Freshdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freshdesk MCP server in PolicyLayer and add a rule for configure_napkin_api_key: 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 Freshdesk. Nothing to install.
configure_napkin_api_key is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the configure_napkin_api_key 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 configure_napkin_api_key. 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.
configure_napkin_api_key is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue