rpc_search_company
Busca una empresa en el Registro Publico de Comercio (SIGER 2.0) por nombre o razon social.
This record as markdown: /tools/inggerman-mcps/rpc-search-company.md
What rpc_search_company does on MCP Framework Personal
AI agents call rpc_search_company to retrieve information from MCP Framework Personal without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why rpc_search_company is rated Low
Even though rpc_search_company only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs rpc_search_company safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rpc_search_company, this is the rule to start with:
rpc_search_company 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 MCP Framework Personal, apply this rule, and every rpc_search_company call is checked against it from then on.
Questions about rpc_search_company
Busca una empresa en el Registro Publico de Comercio (SIGER 2.0) por nombre o razon social. It is categorised as a Read tool in the MCP Framework Personal MCP Server, which means it retrieves data without modifying state.
Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for rpc_search_company: 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 Framework Personal. Nothing to install.
rpc_search_company 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 rpc_search_company 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 rpc_search_company. 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.
rpc_search_company is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Framework Personal, and thousands of servers like it.
This server
Across the catalogue