Get Alfresco repository information using Discovery Client (as tool instead of resource).
AI agents call get_repository_info_tool 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 retrieves metadata and information about the Alfresco repository itself (such as version, capabilities, configuration details). It performs no modifications, deletions, or external operations. Retrieving repository metadata poses minimal risk and is purely informational. Classified as Read with low severity.
From the tool's definition Tool name 'get_repository_info_tool' and description 'Get Alfresco repository information' indicate a retrieval operation. The use of 'Get' and 'Discovery Client' confirms this is a query/fetch operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_repository_info_tool 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 get_repository_info_tool:
{
"version": "1",
"default": "deny",
"tools": {
"get_repository_info_tool": {}
}
} get_repository_info_tool 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.
Get Alfresco repository information using Discovery Client (as tool instead of resource). 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 get_repository_info_tool: 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.
get_repository_info_tool 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_repository_info_tool 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_repository_info_tool. 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_repository_info_tool 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.