get_metadata
A read tool on the Enterprise-Multi-Agent-Engine MCP server.
This record as markdown: /tools/enterprise-multi-agent-engine/get-metadata.md
What get_metadata does on Enterprise-Multi-Agent-Engine
AI agents call get_metadata 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.
Why get_metadata is rated Low
Based on the tool name and the pattern of sibling tools being read-only filesystem operations, 'get_metadata' most likely retrieves file/directory metadata (e.g., size, permissions, timestamps) without modifying state. However, the empty description prevents definitive classification, warranting lower confidence. No evidence of side effects, code execution, or data modification.
From the tool's definition Tool name 'get_metadata' and context of sibling tools ('read_file', 'read_directory', 'list_directory') suggest metadata retrieval; description is empty, reducing confidence.
Attacks that exploit this kind of access
The rule that runs get_metadata 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 get_metadata, this is the rule to start with:
get_metadata 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 Enterprise-Multi-Agent-Engine, apply this rule, and every get_metadata call is checked against it from then on.
Questions about get_metadata
get_metadata is a read tool on the Enterprise-Multi-Agent-Engine MCP server. It is categorised as a Read tool in the Enterprise-Multi-Agent-Engine MCP Server, which means it retrieves data without modifying state.
Register the Enterprise-Multi-Agent-Engine MCP server in PolicyLayer and add a rule for get_metadata: 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.
get_metadata 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_metadata 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_metadata. 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_metadata 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.
More on Enterprise-Multi-Agent-Engine, and thousands of servers like it.
This server
Across the catalogue