get_deputy_by_name
AI agents call get_deputy_by_name to retrieve information from Mcp Camara without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about deputies by name from publicly available legislative data. It performs a read-only query with no side effects, modification of data, or execution of arbitrary code. The blast radius of misuse is minimal, as it only exposes already-public information about government officials and their legislative records.
From the tool's definition Tool name is 'get_deputy_by_name' and sibling tools include 'list_endpoints', 'get_endpoint_schema', 'get_bills_by_deputy', and 'get_deputy_expenses', all of which are read-only query operations against the Brazilian Chamber of Deputies open data API.
Attacks that exploit this kind of access
get_deputy_by_name. It is categorised as a Read tool in the Mcp Camara MCP Server, which means it retrieves data without modifying state.
Register the Mcp Camara MCP server in PolicyLayer and add a rule for get_deputy_by_name: 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 Mcp Camara. Nothing to install.
get_deputy_by_name 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_deputy_by_name 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_deputy_by_name. 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_deputy_by_name is provided by the Mcp Camara MCP server (vrtornisiello/mcp-camara). 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 →