Get SkyFi client factory performance statistics and monitoring info
AI agents call skyfi_factory_stats 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.
This tool retrieves statistics and monitoring information about factory performance. The verb 'Get' and the nature of the data (performance statistics, monitoring info) confirm it is a read-only query operation with no side effects, data modification, code execution, or destructive capabilities.
From the tool's definition Tool name 'skyfi_factory_stats' and description 'Get SkyFi client factory performance statistics and monitoring info' indicate retrieval of read-only monitoring and performance data with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Get SkyFi client factory performance statistics and monitoring info. 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_factory_stats: 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_factory_stats 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_factory_stats 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_factory_stats. 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_factory_stats 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 →