threads_lookup_profile
Look up a public Threads profile by username
This record as markdown: /tools/io-github-alifanov-scopegate/threads-lookup-profile.md
What threads_lookup_profile does on ScopeGate
AI agents call threads_lookup_profile to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why threads_lookup_profile is rated Low
This tool retrieves public profile data from Threads (Meta's social media platform) based on a username query. It is a read-only operation that queries existing data without side effects, modification, deletion, or code execution. The data being accessed is explicitly public, making this a low-severity read operation.
From the tool's definition Tool name 'threads_lookup_profile' and description 'Look up a public Threads profile by username' indicate retrieval of publicly available profile information with no modification or execution of code.
Attacks that exploit this kind of access
The rule that runs threads_lookup_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For threads_lookup_profile, this is the rule to start with:
threads_lookup_profile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every threads_lookup_profile call is checked against it from then on.
Questions about threads_lookup_profile
Look up a public Threads profile by username. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate MCP server in PolicyLayer and add a rule for threads_lookup_profile: 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 ScopeGate. Nothing to install.
threads_lookup_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 threads_lookup_profile 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 threads_lookup_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.
threads_lookup_profile is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue