Get pinned/anchor posts in a room — curated highlights and featured signals.
AI agents call get_anchor_posts to retrieve information from MCP-Networkbot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing curated content (anchor/pinned posts) from a room without side effects. It performs a read-only query operation that returns data to the user. No data is created, modified, deleted, or executed. The low severity reflects that retrieving publicly or semi-publicly shared posts in a professional network poses minimal risk even if accessed by an AI agent.
From the tool's definition Tool name 'get_anchor_posts' and description 'Get pinned/anchor posts in a room' indicate a retrieval operation with the verb 'Get' and no mention of modification, deletion, or execution.
Attacks that exploit this kind of access
Get pinned/anchor posts in a room — curated highlights and featured signals. It is categorised as a Read tool in the MCP-Networkbot MCP Server, which means it retrieves data without modifying state.
Register the MCP-Networkbot MCP server in PolicyLayer and add a rule for get_anchor_posts: 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.
get_anchor_posts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_anchor_posts 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 get_anchor_posts. 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.
get_anchor_posts 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 →