repository_object_search
AI agents call repository_object_search to retrieve information from IBM Content Services MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name and server context clearly indicate this is a search/query function for retrieving documents and metadata from the IBM FileNet repository. Search operations retrieve data without modifying or deleting anything. No side effects are described or implied. Severity is low because searches pose minimal risk even if misused—they expose data but do not alter or destroy it.
From the tool's definition Tool name 'repository_object_search' indicates a search operation. Server description emphasizes 'AI-powered search' as a core capability.
Attacks that exploit this kind of access
repository_object_search. It is categorised as a Read tool in the IBM Content Services MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IBM Content Services MCP Server MCP server in PolicyLayer and add a rule for repository_object_search: 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 IBM Content Services MCP Server. Nothing to install.
repository_object_search 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 repository_object_search 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 repository_object_search. 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.
repository_object_search is provided by the IBM Content Services MCP Server MCP server (mohamedarif-m/filenet-mcp-localfile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →