collect_user_info
AI agents call collect_user_info to retrieve information from Vibe Stack MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or collect user information/preferences as part of a conversational recommendation flow. No destructive, financial, or code execution capabilities are evident. The tool description is empty, which lowers confidence, but the name and server context strongly suggest it queries/collects user data without side effects.
From the tool's definition Tool name 'collect_user_info' in a technology stack recommendation server; sibling tools show patterns of data collection ('collect_features_data', 'collect_project_vision', 'collect_scale_timeline') and information retrieval ('get_deployment_guide',…
Attacks that exploit this kind of access
collect_user_info. It is categorised as a Read tool in the Vibe Stack MCP MCP Server, which means it retrieves data without modifying state.
Register the Vibe Stack MCP server in PolicyLayer and add a rule for collect_user_info: 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 Vibe Stack MCP. Nothing to install.
collect_user_info 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 collect_user_info 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 collect_user_info. 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.
collect_user_info is provided by the Vibe Stack MCP server (memextech/vibe-plan-mcp). 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 →