search_selfemployed
AI agents call search_selfemployed to retrieve information from 企业查询MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to search for self-employed individuals or sole proprietors within an enterprise database. The 'search' prefix indicates read-only querying rather than modification or execution. No modification of data, code execution, deletion, or financial operations are implied. The server context emphasizes data insights and queries, which are characteristic of Read operations.
From the tool's definition Tool name 'search_selfemployed' indicates a search operation. Sibling tools on the server ('search_companies', 'search_established_companies', 'search_established_selfemployed') all follow a search/query pattern consistent with the server description stating…
Documented attack patterns abuse exactly the kind of access search_selfemployed gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 企业查询MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_selfemployed:
{
"version": "1",
"default": "deny",
"tools": {
"search_selfemployed": {}
}
} search_selfemployed is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_selfemployed. It is categorised as a Read tool in the 企业查询MCP MCP Server, which means it retrieves data without modifying state.
Register the 企业查询 MCP server in PolicyLayer and add a rule for search_selfemployed: 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. Nothing to install.
search_selfemployed 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 search_selfemployed 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 search_selfemployed. 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.
search_selfemployed is provided by the 企业查询 MCP server (shuididata/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 企业查询MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 企业查询MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.