schedule_post
AI agents use schedule_post 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.
The tool performs a reversible write operation (scheduling a post) rather than reading, executing arbitrary code, destroying data, or moving money. The medium severity reflects potential for misuse in spamming, impersonation, or manipulation of a professional network, with reversible consequences if posts can be deleted or edited.
From the tool's definition Tool name 'schedule_post' indicates creation/scheduling of content on a professional networking platform. The empty description reduces confidence, but the name and sibling tools (create_mesh_thread, flag_post, browse_members) on a networking server suggest…
Attacks that exploit this kind of access
schedule_post. 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.
Register the MCP-Networkbot MCP server in PolicyLayer and add a rule for schedule_post: 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.
schedule_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the schedule_post 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 schedule_post. 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.
schedule_post 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →