set_talentlms_user_status
Activate or deactivate a user in TalentLMS.\n\n
This record as markdown: /tools/freshdesk/set-talentlms-user-status.md
What set_talentlms_user_status does on Freshdesk
AI agents use set_talentlms_user_status 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 set_talentlms_user_status is rated Medium
This tool creates or modifies user data (account activation state) in TalentLMS. The action is reversible since users can be re-activated or re-deactivated. It does not permanently delete data (Destructive), nor does it move money (Financial) or execute arbitrary code (Execute).
From the tool's definition 'Activate or deactivate a user in TalentLMS' — directly modifies user account status, a reversible state change
Attacks that exploit this kind of access
The rule that runs set_talentlms_user_status 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 set_talentlms_user_status, this is the rule to start with:
set_talentlms_user_status 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 set_talentlms_user_status call is checked against it from then on.
Questions about set_talentlms_user_status
Activate or deactivate a user in TalentLMS.\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 set_talentlms_user_status: 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.
set_talentlms_user_status 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 set_talentlms_user_status 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 set_talentlms_user_status. 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.
set_talentlms_user_status 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