can_send_image

Check if can send image

SERVERNapCat MCP Server SOURCE1021143806/napcat_mcp

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/1021143806-napcat-mcp/can-send-image.md

WHAT IT DOES

What can_send_image does on NapCat MCP Server

AI agents call can_send_image to retrieve information from NapCat MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why can_send_image is rated Low

The tool only queries a capability/feature flag. It retrieves information about whether image sending is supported, making it a pure read operation with minimal blast radius.

From the tool's definition "Check if can send image" — this is a capability check that queries whether the bot supports sending images, with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs can_send_image safely

PolicyLayer is an MCP gateway: it sits between your AI agents and NapCat MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For can_send_image, this is the rule to start with:

can_send_image Allowed

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

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

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

FAQ

Questions about can_send_image

What does the can_send_image tool do? +

Check if can send image. It is categorised as a Read tool in the NapCat MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on can_send_image? +

Register the NapCat MCP Server MCP server in PolicyLayer and add a rule for can_send_image: 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 NapCat MCP Server. Nothing to install.

What risk level is can_send_image? +

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

Can I rate-limit can_send_image? +

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

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

can_send_image is provided by the NapCat MCP Server MCP server (1021143806/napcat_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on NapCat MCP Server, and thousands of servers like it.

This server

All 57 NapCat MCP Server tools →

Across the catalogue

analyze_image on Percepta MCP Server → The MCP Attack Database →

Guides

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