search.semantic.contents
Extract clean text content from up to 10 URLs — returns title, author, published date, full text. Use for feeding web pages into agent context (Exa)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/search.semantic.contents.md
What search.semantic.contents does on Apibase
AI agents call search.semantic.contents to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
urls | array | Yes | URLs to extract content from (1-10). Returns clean text, title, author, date. |
Parameters from the server's own tool schema.
Why search.semantic.contents is rated Low
Tool retrieves and extracts publicly available web content without modifying data or triggering external operations.
From the tool's definition Extract clean text content from URLs — returns title, author, published date, full text.
Attacks that exploit this kind of access
The rule that runs search.semantic.contents safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search.semantic.contents, this is the rule to start with:
search.semantic.contents 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 Apibase, apply this rule, and every search.semantic.contents call is checked against it from then on.
Questions about search.semantic.contents
Extract clean text content from up to 10 URLs — returns title, author, published date, full text. Use for feeding web pages into agent context (Exa). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
search.semantic.contents accepts 1 parameter: urls. Required: urls. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for search.semantic.contents: 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 Apibase. Nothing to install.
search.semantic.contents 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.semantic.contents 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.semantic.contents. 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.semantic.contents is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue