Search for content in Alfresco by metadata fields.
AI agents call search_by_metadata to retrieve information from Alfresco MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation that queries and retrieves information based on metadata criteria. Searches are read-only operations with no side effects on the underlying data. No data is created, modified, deleted, or destroyed. The blast radius of misuse is minimal—an agent could retrieve information it shouldn't access, but cannot alter or destroy content.
From the tool's definition Tool name 'search_by_metadata' and description 'Search for content in Alfresco by metadata fields' indicate a query/retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access search_by_metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Alfresco MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_by_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"search_by_metadata": {}
}
} search_by_metadata 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 for content in Alfresco by metadata fields. It is categorised as a Read tool in the Alfresco MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Alfresco MCP Server MCP server in PolicyLayer and add a rule for search_by_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 Alfresco MCP Server. Nothing to install.
search_by_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 search_by_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 search_by_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.
search_by_metadata is provided by the Alfresco MCP Server MCP server (stevereiner/python-alfresco-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Alfresco MCP Server, 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.
15 Alfresco MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.