configure_kling_api_keys
Save Kling API credentials. Call this when the user provides their API keys.\n\n
This record as markdown: /tools/freshdesk/configure-kling-api-keys.md
What configure_kling_api_keys does on Freshdesk
AI agents use configure_kling_api_keys 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_kling_api_keys is rated Medium
This tool modifies stored credentials/configuration data, which is a Write operation. However, it carries high severity because compromised API keys can lead to unauthorized access to external services (Kling), data breaches, or financial abuse. The tool itself does not delete data (Destructive) or directly move money (Financial), but misuse could enable downstream attacks.
From the tool's definition Tool name 'configure_kling_api_keys' and description 'Save Kling API credentials' indicate the tool creates or modifies stored configuration data (API keys) when invoked.
Attacks that exploit this kind of access
The rule that runs configure_kling_api_keys 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_kling_api_keys, this is the rule to start with:
configure_kling_api_keys 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_kling_api_keys call is checked against it from then on.
Questions about configure_kling_api_keys
Save Kling API credentials. Call this when the user provides their API keys.\n\n. 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_kling_api_keys: 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_kling_api_keys 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_kling_api_keys 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_kling_api_keys. 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_kling_api_keys 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