security_guidelines
AI agents use security_guidelines to create or update resources in Thales Cdsp Csm — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Thales Cdsp Csm environment.
An AI agent can call security_guidelines faster than any human can review — one bad instruction and it creates or modifies resources in Thales Cdsp Csm by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
security_guidelines. It is categorised as a Write tool in the Thales Cdsp Csm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Thales Cdsp Csm MCP server in PolicyLayer and add a rule for security_guidelines: 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 Thales Cdsp Csm. Nothing to install.
security_guidelines 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 security_guidelines 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 security_guidelines. 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.
security_guidelines is provided by the Thales Cdsp Csm MCP server (sanyambassi/thales-cdsp-csm-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 →