post_signal · MCP-Networkbot MCP: Risk & Policy

WHAT IT DOES

What post_signal does on MCP-Networkbot

AI agents use post_signal to create or update resources in MCP-Networkbot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Networkbot environment.

WHY IT NEEDS A POLICY

Why post_signal needs a policy

The name 'post_signal' most naturally maps to creating or publishing content on a network platform, which is a reversible Write operation. Without a description, confidence is moderate, but the sibling tools and server context (networking platform) support this classification.

From the tool's definition Tool name 'post_signal' suggests a write operation that creates or broadcasts a signal/message on the network. The empty description limits certainty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

post_signal Rate-limited

post_signal stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "post_signal": {
      "limits": [
        {
          "counter": "post_signal_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP-Networkbot, so you can run agents against it safely.

FAQ

Questions about post_signal

What does the post_signal tool do? +

post_signal. It is categorised as a Write tool in the MCP-Networkbot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on post_signal? +

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

What risk level is post_signal? +

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

Can I rate-limit post_signal? +

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

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

post_signal is provided by the MCP-Networkbot MCP server (kunalkhanna2007-sys/networkbot-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.