创建一个新的会话
AI agents invoke create_session to trigger actions in WeChat Article Reader MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Creating a session in the context of a browser automation server means spinning up a new browser instance or browser context. This is an Execute-level action because it triggers external operations (launching/initializing browser automation), not merely writing data to a store. Misuse could spawn uncontrolled browser processes or be used to bypass rate limits/access controls.
From the tool's definition '创建一个新的会话' (Create a new session) — involves browser automation initialization as described in the server description ('through browser automation')
Attacks that exploit this kind of access
创建一个新的会话. It is categorised as a Execute tool in the WeChat Article Reader MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WeChat Article Reader MCP Server MCP server in PolicyLayer and add a rule for create_session: 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 WeChat Article Reader MCP Server. Nothing to install.
create_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the create_session 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 create_session. 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.
create_session is provided by the WeChat Article Reader MCP Server MCP server (whbfxy/mcp101demo). 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 →