Get role and permission information for a specific user
AI agents call get_user_roles to retrieve information from Coverity Connect 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 and displays existing user role and permission information from the Coverity Connect platform. It has no side effects, does not modify data, and does not execute code or trigger external operations. The read operation carries minimal risk as it simply returns information about user entitlements.
From the tool's definition Tool name 'get_user_roles' and description 'Get role and permission information for a specific user' indicate a read-only retrieval operation that queries user metadata without modifying any data.
Documented attack patterns abuse exactly the kind of access get_user_roles gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Coverity Connect MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user_roles:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_roles": {}
}
}get_user_roles is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get role and permission information for a specific user. It is categorised as a Read tool in the Coverity Connect MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Coverity Connect MCP Server MCP server in PolicyLayer and add a rule for get_user_roles: 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 Coverity Connect MCP Server. Nothing to install.
get_user_roles 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_user_roles 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_user_roles. 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_user_roles is provided by the Coverity Connect MCP Server MCP server (keides2/coverity-connect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Coverity Connect MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Coverity Connect MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.