get_presence
Get your current presence status (available, busy, away, etc.).
This record as markdown: /tools/freshdesk/get-presence.md
What get_presence does on Freshdesk
AI agents call get_presence to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_presence is rated Low
This tool queries the current presence status of a user, which is a read-only operation that retrieves data without creating, modifying, deleting, or executing any actions. The low severity reflects that presence status information has minimal security impact if accessed by an AI agent.
From the tool's definition Tool name 'get_presence' and description 'Get your current presence status' indicate retrieval of user status information with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_presence 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 get_presence, this is the rule to start with:
get_presence 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 Freshdesk, apply this rule, and every get_presence call is checked against it from then on.
Questions about get_presence
Get your current presence status (available, busy, away, etc.). It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for get_presence: 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.
get_presence 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_presence 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_presence. 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_presence 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