napkin_check_status

Check the status of a Napkin visual generation request. REQUIRED after calling napkin_generate_visual.

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/napkin-check-status.md

WHAT IT DOES

What napkin_check_status does on Freshdesk

AI agents call napkin_check_status 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 napkin_check_status is rated Low

This tool retrieves the status of an asynchronous visual generation request without modifying, executing, or deleting any data. It is a read-only operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'napkin_check_status' and description 'Check the status of a Napkin visual generation request' indicate a query/polling operation to retrieve status information.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

napkin_check_status Allowed

napkin_check_status 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": {
    "napkin_check_status": {}
  }
}

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 napkin_check_status call is checked against it from then on.

FAQ

Questions about napkin_check_status

What does the napkin_check_status tool do? +

Check the status of a Napkin visual generation request. REQUIRED after calling napkin_generate_visual. 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 napkin_check_status? +

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

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

Can I rate-limit napkin_check_status? +

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

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

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

KEEP EXPLORING

More on Freshdesk, and thousands of servers like it.

This server

All 422 Freshdesk tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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