set_talentlms_user_status

Activate or deactivate a user in TalentLMS.\n\n

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about set_talentlms_user_status

What does the set_talentlms_user_status tool do? +

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.

How do I enforce a policy on set_talentlms_user_status? +

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.

What risk level is set_talentlms_user_status? +

set_talentlms_user_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_talentlms_user_status? +

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.

How do I block set_talentlms_user_status completely? +

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.

What MCP server provides set_talentlms_user_status? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Freshdesk's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.