find_app_components

Search components in the app catalog by name, englishName, or guid.

SERVEREnterprise-Multi-Agent-Engine SOURCEMojtaba-Dehghani/Enterprise-Multi-Agent-Engine

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/enterprise-multi-agent-engine/find-app-components.md

WHAT IT DOES

What find_app_components does on Enterprise-Multi-Agent-Engine

AI agents call find_app_components to retrieve information from Enterprise-Multi-Agent-Engine without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why find_app_components is rated Low

Tool retrieves and queries app component metadata without modifying or executing any operations.

From the tool's definition Search components in the app catalog by name, englishName, or guid.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_app_components safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Enterprise-Multi-Agent-Engine, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_app_components, this is the rule to start with:

find_app_components Allowed

find_app_components is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "find_app_components": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Enterprise-Multi-Agent-Engine, apply this rule, and every find_app_components call is checked against it from then on.

FAQ

Questions about find_app_components

What does the find_app_components tool do? +

Search components in the app catalog by name, englishName, or guid. It is categorised as a Read tool in the Enterprise-Multi-Agent-Engine MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_app_components? +

Register the Enterprise-Multi-Agent-Engine MCP server in PolicyLayer and add a rule for find_app_components: 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 Enterprise-Multi-Agent-Engine. Nothing to install.

What risk level is find_app_components? +

find_app_components is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit find_app_components? +

Yes. Add a rate_limit block to the find_app_components 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.

How do I block find_app_components completely? +

Set action: deny in the PolicyLayer policy for find_app_components. 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.

What MCP server provides find_app_components? +

find_app_components is provided by the Enterprise-Multi-Agent-Engine MCP server (Mojtaba-Dehghani/Enterprise-Multi-Agent-Engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Enterprise-Multi-Agent-Engine, and thousands of servers like it.

This server

All 262 Enterprise-Multi-Agent-Engine tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →