vanta_get_control

Get details for one Vanta control by ID.

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/freshdesk/vanta-get-control.md

WHAT IT DOES

What vanta_get_control does on Freshdesk

AI agents call vanta_get_control 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.

RISK

Why vanta_get_control is rated Low

This tool queries and retrieves control information from Vanta without modifying, executing, or deleting any data. The verb 'get' and the absence of any mutating operations place it squarely in the Read category. The blast radius of misuse is minimal—worst case, an agent could retrieve sensitive control details, but no data is altered or operations are triggered.

From the tool's definition Tool name 'vanta_get_control' and description 'Get details for one Vanta control by ID' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vanta_get_control 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 vanta_get_control, this is the rule to start with:

vanta_get_control Allowed

vanta_get_control is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vanta_get_control": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every vanta_get_control call is checked against it from then on.

FAQ

Questions about vanta_get_control

What does the vanta_get_control tool do? +

Get details for one Vanta control by ID. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vanta_get_control? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for vanta_get_control: 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 vanta_get_control? +

vanta_get_control is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit vanta_get_control? +

Yes. Add a rate_limit block to the vanta_get_control 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 vanta_get_control completely? +

Set action: deny in the PolicyLayer policy for vanta_get_control. 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 vanta_get_control? +

vanta_get_control 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.

KEEP EXPLORING

More on Freshdesk, and thousands of servers like it.

This server

All 422 Freshdesk tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →