Search SkyFi archive using client factory for optimized performance
AI agents call skyfi_archive_search_with_factory to retrieve information from SkyFi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is described as searching the SkyFi archive, which is a read/query operation. The 'client factory for optimized performance' is an implementation detail about how the search is performed, not about side effects. No write, execute, destructive, or financial actions are implied.
From the tool's definition "Search SkyFi archive" — the tool performs a search/retrieval operation on the SkyFi archive
Attacks that exploit this kind of access
Search SkyFi archive using client factory for optimized performance. It is categorised as a Read tool in the SkyFi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SkyFi MCP Server MCP server in PolicyLayer and add a rule for skyfi_archive_search_with_factory: 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 SkyFi MCP Server. Nothing to install.
skyfi_archive_search_with_factory 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 skyfi_archive_search_with_factory 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 skyfi_archive_search_with_factory. 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.
skyfi_archive_search_with_factory is provided by the SkyFi MCP Server MCP server (pskinnertech/skyfi-mcp-server). 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 →