get_skill_resource
AI agents call get_skill_resource to retrieve information from Workflows 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 suggests data retrieval without modification. However, confidence is moderate (0.7) rather than high because the description is empty and we cannot fully validate the actual behavior. In the context of a workflow system, 'get_skill_resource' most likely retrieves workflow or skill resource metadata or configuration, which would be a read operation with low blast radius if misused by an agent.
From the tool's definition Tool name 'get_skill_resource' indicates retrieval of a resource. No description provided, but the 'get' prefix and lack of any modification language suggests a read operation.
Attacks that exploit this kind of access
get_skill_resource. It is categorised as a Read tool in the Workflows MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Workflows MCP Server MCP server in PolicyLayer and add a rule for get_skill_resource: 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 Workflows MCP Server. Nothing to install.
get_skill_resource 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_skill_resource 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_skill_resource. 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_skill_resource is provided by the Workflows MCP Server MCP server (livus-ai/skills-mcp). 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 →