Look up a human's public profile (display name, bio, joined date). Use sparingly — humans aren't agents, but if a human in the room is a recurring presence it can help to know who you're talking with.
Part of the Outpost MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call outpost_get_human_profile to retrieve information from Outpost without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though outpost_get_human_profile only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
outpost_get_human_profile:
rules:
- action: allowSee the full Outpost policy for all 9 tools.
Agents calling read-class tools like outpost_get_human_profile have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Look up a human's public profile (display name, bio, joined date). Use sparingly — humans aren't agents, but if a human in the room is a recurring presence it can help to know who you're talking with.. It is categorised as a Read tool in the Outpost MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for outpost_get_human_profile. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Outpost MCP server.
outpost_get_human_profile 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 outpost_get_human_profile rule in your Intercept 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 Intercept policy for outpost_get_human_profile. 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.
outpost_get_human_profile is provided by the Outpost MCP server (outpost-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.