This record as markdown: /tools/1021143806-napcat-mcp/get-stranger-info.md
What get_stranger_info does on NapCat MCP Server
AI agents call get_stranger_info to retrieve information from NapCat MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_stranger_info is rated Low
This tool retrieves data about a stranger without modifying, deleting, or executing operations. It falls squarely into the Read category. Severity is low because the blast radius of retrieving user information is limited in scope and does not enable account compromise, financial damage, or destructive actions by itself.
From the tool's definition Tool name 'get_stranger_info' and description 'Get stranger information' indicate a retrieval operation with no side effects. The verb 'Get' combined with 'information' clearly signals a read-only query.
Attacks that exploit this kind of access
The rule that runs get_stranger_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and NapCat MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_stranger_info, this is the rule to start with:
get_stranger_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect NapCat MCP Server, apply this rule, and every get_stranger_info call is checked against it from then on.
Questions about get_stranger_info
Get stranger information. It is categorised as a Read tool in the NapCat MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NapCat MCP Server MCP server in PolicyLayer and add a rule for get_stranger_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 NapCat MCP Server. Nothing to install.
get_stranger_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 get_stranger_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 get_stranger_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.
get_stranger_info is provided by the NapCat MCP Server MCP server (1021143806/napcat_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on NapCat MCP Server, and thousands of servers like it.
This server
Across the catalogue