AI agents use clelp_rate to create or update resources in Clelp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clelp environment.
This tool submits a user rating for a skill, which is a write operation that creates new data (a rating). It is reversible in principle (ratings can be updated or removed) and has low blast radius since it only affects community rating data, not critical systems.
From the tool's definition 'Submit a rating for a skill' — creates/posts a rating entry
Attacks that exploit this kind of access
Submit a rating for a skill you. It is categorised as a Write tool in the Clelp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clelp MCP server in PolicyLayer and add a rule for clelp_rate: 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 Clelp. Nothing to install.
clelp_rate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the clelp_rate 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 clelp_rate. 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.
clelp_rate is provided by the Clelp MCP server (oscarsterling/clelp-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 →